First project

Open a folderCopy Anchor Link

In the workbench, click Open project folder and choose an existing folder or create a new one. The desktop app uses the system folder picker; in a browser you browse real folders on the daemon’s machine, or type an absolute path.

The folder is the project’s identity. Opening the same folder again (including with a trailing slash or through a symlink) reuses the same project ID, prompt, skills and sessions without re-initializing.

The CLI equivalent:

./rna project-new "Checkout redesign" "Move checkout to the new design system with all regression tests passing" --workspace /absolute/path/to/shop
./rna project-open /absolute/path/to/shop   # registers first, reuses after
./rna project PROJECT_ID                    # initialization progress and capability assignments

What initialization doesCopy Anchor Link

Initialization is queued in the background and generated by your chosen model from the title and description:

• a project overview, current focus and milestones;
• the project prompt and the skills, tools and MCP it needs, each with a reason;
• editable acceptance criteria, and a project capability package that passed real script smoke checks.

Without a real model the project stays “waiting to initialize”; no template pretends to be model output. Retry on failure:

./rna project-init PROJECT_ID

Start talkingCopy Anchor Link

A project can have several sessions. Each keeps its full history, progress and drafts. A finished turn does not end the session, and closing a session does not stop the project’s initiative.

./rna new "Implementation" --project PROJECT_ID
./rna chat SESSION_ID

Describe what you want, for example “check the checkout layout at 390px width”. While it works you can:

• Steer: affects the current turn at the next safe boundary;
• Queue: handled right after this turn;
• Withdraw: anything not yet in the context can be taken back;
• Stop: stops this turn only; the project’s background work continues.

Archive and deleteCopy Anchor Link

The “⋯” menu on projects and sessions offers rename, archive and delete.

• Archive keeps history and the outgoing queue and pauses running work. Unarchiving restores visibility only; paused paid requests need you to continue them.
• Deleting a session removes chat records, attachments and session-only runtime files. Files in the project folder and extracted project memory stay.
• With unfinished execution or a failed remote cleanup, the state stays “pending cleanup” instead of pretending it is gone.