Documents

Open it#

Use the right rail's Generate PDF (Project overview, Onboarding guide, Architecture or Ask for anything), the Docs chip in the open thread, or say open documents. Choosing an item only selects it; nothing is generated until you press Generate.

Generate a document#

1. Pick the CLI

   Your default agent comes first, then Claude, Codex, Gemini, Grok and OpenCode, and any catalog agent you add with +. Agents that are not installed are dimmed.

2. Pick the effort

   Quick

   Fastest, shorter and less polished. Good for a first look.

   Balanced

   The default.

   Thorough

   Slowest; the longest, most careful result.

   Each option shows the median time of your last five finished runs with the selected CLI on this Mac, or not timed until one has finished. Quick asks for about 400 to 700 words, Balanced 700 to 1,100, Thorough 900 to 1,500.

3. Pick the document

   Project overview, Onboarding guide, Architecture, README, API reference, Data model, Security overview, Testing guide or Release notes. Or describe your own in Ask for anything, for example a migration plan from REST to GraphQL.

4. Generate

   A status line follows the run (launching, thinking, writing, finishing) with the agent's name and the time. The page streams in as it is written. Stop keeps what arrived.

How it works#

• Symvibe starts your CLI in a terminal you do not see, in the repo's folder and under the account new consoles use. It types one prompt, reads the answer off the screen, then closes the session. It never uses a print mode or an API, and never adds Yolo flags.
• The prompt tells the agent not to run tools or open files. It writes from what it can see when it starts in your repo, such as the folder and the project notes it loads by itself, like a CLAUDE.md.
• Each run is one real turn on your plan, like a prompt you type. Like any session of your CLI, it may appear in the CLI's own history.
• If the CLI stops on a question Symvibe will not answer for you, such as whether to trust the folder or a sign-in screen, the run ends and tells you what to do: open a console in the repo, answer it there, and try again. A Codex update prompt is skipped, never installed.

• Documents are written in English.
• A run is stopped after 6, 12 or 25 minutes of work depending on the effort, counted from when the prompt is sent, or after 200 seconds without any output. Quick effort or a narrower ask helps.

The library#

• Every finished or stopped run is saved as a new version, per repo, with its date and agent. A run that did not finish is marked Incomplete and offers Regenerate and Export draft PDF.
• Choosing a document that already has versions opens the newest. Generate again asks again with the CLI selected now.
• Versions are kept in ~/Library/Application Support/Hypervibe/Documents, one folder per repo, named after the repo's folder plus a short code made from its full path.
• Remove from library deletes a version for good. It does not go to the Trash.

Preview and export#

• Switch between a flowing preview and a page-by-page preview that is exactly what the PDF will be.
• Export PDF uses US Letter by default, or A4. The PDF has a cover with the title, the agent, the repo and the date, a contents page when there are three or more headings, running headers, page numbers and bookmarks. It is always printed on the light theme.
• The export menu also has Export Markdown and Copy Markdown.
• Images in generated documents appear as labelled placeholders.
• Add to board places the document on the board as a card with its own Export PDF.

Keep going#