The planning workspace for Claude Code.

As a developer, your planning already lives in markdown. Specs, architecture notes, Claude Code plans, project docs — they're all .md files. Moss is the notes app for developers that fits into that workflow: everything stored on disk, everything in plain text, ready to open in any editor or commit to a git repository. Most notes apps make you choose between power and portability. Your docs are locked in a cloud database, or you need a bunch of plugins for anything beyond basic linking. Moss gives you a full-featured markdown editor for developers — plus a built-in AI agent that annotates specs, researches implementation options, and hands off work to Claude Code — without configuration or compromise.

The hardest part of working with Claude Code isn't generating plans — it's reviewing them. Moss lets you open your Claude Code project directory and annotate plans with inline comments directly on the markdown file. Flag sections for revision, leave feedback on specific paragraphs, and let Claude Code pick up the changes. No copy-pasting into a chat window. No separate review tool. The same inline comment system works for specs, architecture docs, and any other planning document. Write a spec in Moss, review it with comments, and share the .md file with teammates via git. A review workflow built around files, not platforms.

Moss opens any folder of markdown files: your Claude Code project directory, your Obsidian vault, a repo's /docs folder, a collection of project notes. No importing, no migration, no conversion step. Point Moss at the directory and start working. Edit in Moss, open the same file in VS Code, commit to git from the terminal — everything stays in sync because it's all just files on disk.

Moss is built around the same file format Claude Code uses for plans and specs. Open your project directory in Moss, use the AI agent to research implementation options or expand a spec, leave inline comments on sections you want revised, and Claude Code picks up the result. The handoff is seamless because both tools read and write plain .md files. There's no proprietary layer to work around.

Every note in Moss is a file on your computer. Work offline. Version your notes with git alongside your code. Open notes in VS Code, run scripts against them, or reference them in any markdown-aware tool. There's no cloud account required, no proprietary database, and no export step if you ever want to move on. The file-first architecture means Moss fits into your existing developer workflow — not the other way around.

When you're writing a spec or planning an architecture, you often need to look things up. Moss's AI agent searches the web, pulls in relevant sources, scans your codebase if you give it access, then it writes findings directly into your note — without you leaving the document. Ask it to compare two database options, summarize a library's API, or draft a technical section from a rough outline. The agent works inside your notes, not in a separate chat window, so the research stays connected to the work it informs.

Yes. Moss reads and writes standard .md files: the same format Claude Code uses for plans, specs, and project docs. Open your project directory in Moss, annotate specs with inline comments, and Claude Code picks up the changes. You can leave feedback directly on the plan, flag sections for revision, and use Moss's AI agent to research or expand specs, all without switching tools or copying content into a chat window.

Moss is a full-featured notes app built around markdown from the ground up. Every note lives on disk as a .md file, so it works alongside your code editor, syncs naturally with git, and opens in any tool that reads markdown. There's no proprietary database, no importing step, and no account required. It's the same file format you're already writing in. Moss just adds a collaborative AI layer on top.

Yes. Point Moss at any folder — your Claude Code project directory, your Obsidian vault, a repo's /docs folder, a directory of project docs — and it opens them as-is. No importing, no migration, no conversion step. Moss treats your files as the source of truth. Edit in Moss, open the same file in VS Code, commit to git from the terminal — everything stays in sync because it's all just files.

Obsidian is a personal knowledge graph built around linking notes together. Moss is built around doing work inside notes — inline AI editing, web research, data analysis, and Claude Code handoff. Both use local markdown files, but Moss's AI agent actively collaborates on the page: it annotates specs, drafts sections, and searches the web without you switching tabs. Obsidian requires plugins for most of this; Moss includes it natively and doesn't require any configuration.

No. Moss does not use your notes, specs, or code plans to train AI models. The AI agent runs on Claude (Anthropic). Queries are sent to process your request and nothing is retained for training. Your notes, architecture docs, and planning files stay private. If you connect your own Anthropic API key, the same standard Anthropic privacy policy applies directly.

Moss is currently designed for individual use. Notes live on your machine, which means they're yours. There's no shared workspace or multiplayer editing yet. Many developers use Moss for personal spec work and planning, then share the resulting .md files with teammates via git. Since notes are plain files, they're already version-controllable and shareable the same way code is.

Not yet natively, but it doesn't need to: your notes are already plain .md files on disk. Drop a Moss note into any git repository and version it like any other file. Many developers keep their Moss notes directory inside a repo and commit notes alongside code. First-class git sync is on the roadmap as a feature; right now the file-first architecture means standard git workflows already work.

Nothing changes. Your notes are standard markdown files on your hard drive. Stop using Moss and open them in VS Code, iA Writer, Obsidian, or any text editor. They're just files. There's no proprietary format, no export step, and no data held hostage. This is the whole point of building on plain text: your notes belong to you, not to the app.

Completely. Notes are files on your computer. Read, write, and organize without an internet connection. The AI agent requires a connection when you use it (it calls the Claude API), but the notes app itself works fully offline. No account required to get started, and no account ever required if you only want the markdown editor.