Notexs
Roadmap

A roadmap for where Notexs goes next.

Notexs is becoming a local-first workspace for turning rough notes, research, references, and project context into work you can review, share, export, and hand off with confidence.

Product thesis

Keep the source material close to the final work.

The goal is not another chat wrapper, another social knowledge feed, or another locked-in document tool. The goal is a calm desktop workspace where notes, sources, diagrams, previews, and exports stay connected.

AI belongs in that workflow, but as a connector: explicit, user-controlled, and compatible with the tools people already use.

01

Local-first should feel dependable, not isolated.

02

Markdown should stay readable, portable, and editable.

03

AI should connect to the workspace without owning it.

04

Documents should come from the same place where thinking happens.

05

Sharing should be intentional, useful, and quiet.

Roadmap

Priorities by confidence, not by public deadlines.

This is written as direction on purpose. Dates will appear only when the work is close enough to be useful and honest.

01

Now

Actively hardening

The compact workspace layer: notebooks, notes, diagrams, local storage, and the desktop foundation.

  • Tree-based workspace as the primary layout
  • Markdown notes with notebook-first organization
  • Mermaid rendering with optional animation
  • Local SQLite storage and desktop distribution
  • Initial MCP bridge for external AI tools
02

Next

Planned product work

The workflow layer: cleaner note creation, better exports, and AI connector setup that stays BYOK-friendly.

  • New note flows with blank and template starts
  • Better document export and publishing paths
  • AI connector setup for Claude, ChatGPT, Gemini, and local tools
  • Optional cloud backup and account continuity
  • Cleaner diagram, asset, and reference workflows
03

Exploring

Promising, not promised

Directions that fit Notexs, but still need validation before becoming real commitments.

  • Controlled sharing for small teams
  • Public docs or lightweight knowledge sites
  • Workflow automation and app triggers
  • Versioned deliverables and review states
  • Importer and integration surface for power users
04

Not chasing yet

Intentionally out of focus

Things that would make the product feel bigger before it feels better.

  • A public social network or empty forum
  • Chat as the main interface for everything
  • Cloud-only workspace behavior
  • Locked-in proprietary note formats
  • Enterprise theater before the product is ready

Long-term direction

Technical writing workbench

Local knowledge base

Deliverable engine

MCP bridge

Publishing layer

Workflow automation

Built independently by Cesar Arguijo and shaped by early users doing real technical work.

Progress should be visible.

The changelog is the public proof of movement. It should show what actually shipped, what changed, and how Notexs is becoming more useful over time.