Skip to content

Add Install and TUI Quickstart to the README#80

Open
MJohnson459 wants to merge 1 commit into
mainfrom
worktree-readme-quickstart
Open

Add Install and TUI Quickstart to the README#80
MJohnson459 wants to merge 1 commit into
mainfrom
worktree-readme-quickstart

Conversation

@MJohnson459

Copy link
Copy Markdown
Contributor

Add Install and Quickstart sections to README.md.

Install: matches the cargo-dist release pipeline (#118/#77). Documents the prebuilt shell installer (curl … releases/latest/download/voro-installer.sh | sh, lands in ~/.cargo/bin), the per-platform Release tarballs (x86_64-unknown-linux-gnu, aarch64-apple-darwin) with checksums, and the from-source path (cargo install --git https://github.com/ClachDev/Voro voro). Notes Voro is Unix-only and ships a single voro binary.

Quickstart: a TUI-centred operator walkthrough — launch the cockpit with bare 'voro', then register a project (Projects screen, 'a'; weight via 0-5), create a task ('n' editor / 'N' planning session, body = the agent's prompt), triage it into the queue (⏎ triage), dispatch ('d' / 'D' agent pick), and review the result ('o' checkout / 'g' PR, ⏎ review, reject-with-note re-dispatches). Frames the return-path verbs (ask/done/propose) as the agent's interface, not the operator's, and links docs/agent-integration.md. No invented keys — all taken from the ui.rs footer legend and app.rs key handling; no 'skill' system described.

Existing sections (Design, Building, Releasing, Dispatching, License) are unchanged.

Verified: install command/URL and tarball triples against dist-workspace.toml and .github/workflows/release.yml; every named key against crates/voro/src/ui.rs (key_hints) and crates/voro/src/app.rs (on_key/enter_hint); CLI verbs against crates/voro/src/cli.rs. Docs-only change.

The README covered purpose, build-from-source, and dispatch internals but gave
an end user no download-and-run path and no walkthrough of the human workflow.

Add an Install section matching the cargo-dist release pipeline (#77): the
prebuilt `voro-installer.sh` shell installer, the per-platform Release tarballs
(x86_64 Linux, aarch64 macOS), and the from-source `cargo install --git` path.
Note Voro is Unix-only and ships a single `voro` binary.

Add a Quickstart that drives the TUI cockpit end-to-end — register a project,
create a task (`n`/`N`), triage it (`⏎ triage`), dispatch (`d`/`D`), and review
the diff (`o`/`g`, `⏎ review`). Keys are taken from the ui.rs footer legend and
app.rs key handling; the return-path verbs are framed as the agent's interface,
not the operator's.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NimpS2bBUqN6qFNBXGZfjx
Comment thread README.md
binary for your platform and drops it in Cargo's bin directory (`~/.cargo/bin`):

```bash
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/ClachDev/Voro/releases/latest/download/voro-installer.sh | sh

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need all these args?

Comment thread README.md
To build and install from source instead:

```bash
cargo install --git https://github.com/ClachDev/Voro voro

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming we push to crates this can be simplified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant