Document-driven Vibe Coding

The project documentation IDE for the AI era.

From requirements to delivery, help your Agent write clear, consistent project documentation that follows your standards.

Download for macOS Download for Windows Download for Linux

Agents that support SkillsClaude Code · Codex · Cursor · Gemini CLI · ZCode · DSH · OpenCode · GitHub Copilot, and more

issues · Doc specs Get started Offline sync v1 implementation · plan
VibeNoteissues· Doc Spec
Document propertiesAgent rules Save as template…
Table Board New
Edited Status: to confirm, to do, in progress Filter Reset
Requirement3
DocumentTypeStatusPriorityCreatorCreatedEdited
Command palette for quick navigation Requirement To do — you2026-11-08 09:122026-11-08 09:12
Import from bookmarks HTML file Requirement In progress — you2026-11-06 15:402026-11-07 09:15
Pinned documents at the top of the vault Requirement To do Medium you2026-10-28 10:312026-10-28 10:32
New document
BUG0
DocumentTypeStatusPriorityCreatorCreatedEdited
New document
Task1
DocumentTypeStatusPriorityCreatorCreatedEdited
Reduce cold-start time on large vaults Task In progress High you2026-11-05 10:202026-11-09 09:18
New document
Question0
DocumentTypeStatusPriorityCreatorCreatedEdited
New document
New group
issues · Doc specs Get started Offline edits create duplicate entries after sync Meet VibeNote
VibeNote Meet VibeNote EditPreview
Meet VibeNote
CreatedNov 4, 2026 10:12:00
EditedNov 9, 2026 09:30:00
Add property

Learn how documents are organized, and start writing and maintaining them with your Agent.

The vault and documents

A vault keeps a set of related documents. Organize them by project, browse them in the document tree, and follow the latest Agent edits in the recent list.

The vault

Browse the tree from the main sidebar, or switch to the Recent view to see what changed.

  • Create, import, or clone a vault
  • Sync and collaborate with your team
Documents and document specs

Every document is plain Markdown. A folder can carry a document spec: the properties and writing rules every document in it follows — written by you, kept by your Agent.

  • Hand documents to your Agent
  • Define your Agent writing rules
Open the folder's document spec

Select a folder, open Doc Spec, and declare the properties and writing rules. Your Agent reads them before it writes a single line.

Organize the vault

Create folders per project and keep the structure consistent with the project template, so the whole team works the same way.

Let your Agent maintain documents

Hand documents to your Agent to draft, revise and summarize. Writing rules live in AGENTS, and the Agent follows them.

Annotations discuss the specifics: select a range, write your comment, and the Agent addresses them one by one.

What's next

Open any folder in the sidebar, or create a document and start writing. The outline and annotations are always at hand.

1,248 tokens2,314 chars 0 remarks3 versions 0 AI annotations2 refs
issues · Doc specs Get started Offline sync v1 implementation · plan Conflict resolution for offline edits Meet VibeNote
VibeNote plans Offline sync v1 implementation · plan EditPreview
Offline sync v1 implementation · plan
Document typePlan
StatusDone
CreatedNov 9, 2026 04:02:21
EditedNov 9, 2026 06:48:12
Authorsyou
Goals and basis

Implement Conflict resolution for offline edits, resolving Offline edits create duplicate entries after sync with automated verification.

Task orchestration

Tasks run in dependency order. Merge changes can be written independently; this round shares one regression goal and one code snapshot, integrated serially.

R1Done
Build the sync regression evidence
Prove the duplicate-entry path on a controlled host with scripted offline edits.
R2Done
Implement the offline merge intent
Recognize offline revisions during sync and keep one entry per edit, per the design.
R3Done
Finish boundary verification and wrap-up
Verify the affected sync paths with the smallest relevant gate, and record results.
4,522 tokens8,470 chars 0 remarks6 versions 0 AI annotations2 refs

Edit and manage project documents with your Agent.

01Collaboration challenges

More documents call for consistent writing and clear organization.

As project documents grow, writing, reviewing and organizing them need the right tools.

1

The same document type, different structures

Sections, terms and writing styles vary between similar documents. Each one takes extra effort to read and maintain.

2

Changes are hard to review

An Agent can change several documents in one pass. Finding each file and checking its edits makes review tedious.

3

A new session needs the context again

Requirements and design decisions stay in chat. A new session or Agent needs them explained again.

4

More documents, less clarity on progress

Requirements, bugs and plans are scattered across files. Priorities, status and execution progress are hard to see together.

02The basic workflow

One requirement connects the design and the plan.

Record requirements, decisions and planned work in documents so your Agent can build on what is already there.

Step 1 · Requirement

Record the requirement

Create an issue for a requirement, bug or question. State the request and what completion means.

issues/
Step 2 · Design

Discuss the design

Draft the design with your Agent and discuss its scope and tradeoffs. Keep lasting rules in a spec.

designs/ specs/
Step 3 · Implementation

Plan the work

Break work into tasks in a plan. A workflow defines dependencies and acceptance criteria; your Agent executes the nodes and updates their status.

plans/ workflow
Documents for one requirement
ISSUE Single-click preview and double-click keep in document tree and list Resolved
→
DESIGN Document open interaction unified design Finalized
→
PLAN Document open interaction unified implementation workflow with 3 nodes, completed

Write results back to the plan and issue, and keep decisions current in the documents.

03Built-in capabilities

Write consistently. Review clearly. Stay organized.

ManageFrom document structure to issue status

Project templates

Start a project with document folders and matching standards already in place.

Project template

Multi-dimensional table

Manage issues in tables and boards. Group and filter them by type, status and priority.

Table / board · for issues
WriteHelp your Agent follow your standards

Document specs

Define properties, sections and writing rules for a folder so documents of the same type follow the same structure.

AGENTS · Git

Writing Skill

The writing Skill applies STE principles, guiding your Agent to use short sentences and consistent terms for clear, readable documents.

SKILL.md

AI annotations

Annotate a passage and discuss specific changes with your Agent.

Multi-round · archived
ReviewSee changes and execution progress

Recent

Find recently changed documents in one list, grouped by time. Open one to start reviewing.

By time · straight to the doc

Diff rail

Locate changes beside the text and review your Agent’s edits passage by passage.

Change location

Workflow orchestration

View planned tasks as a flowchart, with dependencies and execution status for each node.

Nodes · dependencies · status
04AI annotations

Discuss designs with your Agent, one annotation at a time.

Annotate details your Agent needs confirmed or changes you want in a draft. Reply to each question separately and keep the conclusions with the document.

Example: an offline sync design

Discuss in chat

Questions follow one conversation timeline.

Agent

Design draft:

  1. Keep the latest version on conflict.
  2. Sync text and attachments in v1.
  3. Retry automatically on failure.
You

Can we keep both versions when edits conflict?

Agent

Yes. I have updated conflict handling.

You

We still need to discuss attachments and retries. I also have another point about conflicts…

Annotate beside the text

Mark questions together; reply and resolve them separately.

1

Conflict handling

Resolved
Keep the latest version on conflict.

YouCan we keep both versions?

AgentUpdated to keep both versions.

2

Scope of v1

Discussing
Sync text and attachments in v1.

YouCan attachments wait?

AgentYes. Shall v1 sync text only?

3

Failure handling

Discussing
Retry automatically on failure.

YouHow many retries? How is failure shown?

AgentI suggest three retries, then a failure status.

05Sync and collaboration

Personal sync and team collaboration.

Built-in Git and autosave support work across devices and shared team vaults.

Personal sync

Switch devices and keep editing

Sign in and clone a hosted vault to your new device to continue editing.

  1. 01Sign in
  2. 02Choose your vault
  3. 03Clone locally
Team collaboration

Maintain a shared vault as a team

Share a vault so members can clone it to their devices and maintain its documents with their own Agents.

  1. 01Share with your team
  2. 02Members clone
  3. 03Work together

Frequently asked questions

Why use VibeNote instead of Obsidian?+

VibeNote is built primarily for editing and managing project documents with Agents, with four capabilities included:

  • Find changed documents. Open Recent to go straight to documents that need review.
  • See the actual edits. Diff rail marks changes beside the document text.
  • Keep structure and writing consistent. The writing Skill and your document standards guide the Agent.
  • Use less memory. The native Rust and GPUI client runs alongside your Agent tools.

Obsidian has a rich plugin ecosystem. VibeNote brings these collaboration capabilities together in the product.

Can I also use VibeNote for personal notes?+
Yes. Markdown suggestions, a syntax menu and centralized asset management support everyday editing. Paste or drop images, and ask your Agent to create or revise diagrams.
Can I use VibeNote as a general-purpose Markdown editor?+
Yes. Open and edit local Markdown files directly.
Which Agents can I use?+
Tools that support Agent Skills can connect to VibeNote. Install the VibeNote Skill, then give your Agent the document URI and your request.
What is the workflow in a plan?+
A workflow is a task orchestration block in a plan for your Agent. Each node contains a goal, task list and acceptance criteria. Dependencies connect the nodes, and the flowchart shows execution status.
What format are documents stored in?+
Documents are stored as plain Markdown, with history managed by Git. You can open and edit them with other compatible tools.

Your next requirement starts with an issue.

Create or import a vault, set up its structure with a project template, and record your first requirement with your Agent.

Download for macOS Download for Windows Download for Linux