Stvena

Your coding agent. Your changes. One terminal.

Agent.Navigator.Demo.mp4

Stvena runs your coding agent beside a live code review workspace. Keep the agent's native terminal experience while you inspect changes, read complete files, collect context, and run checks against the code you are reviewing.

Built in Go. Designed for terminal workflows with Codex and Claude Code. Early-stage software: interfaces and local storage formats may change.

Why Stvena?

• See the work as it happens. Review changes since the agent started, or inspect staged, unstaged, and new files across the workspace.
• Read beyond the diff. Browse the project tree, open complete files, and switch between unified and side-by-side views with syntax highlighting.
• Give the agent precise context. Select code with the mouse or keyboard, collect snippets across files, and paste an assembled draft into the agent. You decide when to submit it.
• Keep track of your review. Pin a captured version, mark files and hunks reviewed, and see when a reviewed change has changed again.
• Check the code you are looking at. Run a command in a temporary checkout of a captured version, inspect logs, and jump from recognized failures to source.
• Stage deliberately. Stage or unstage files and hunks with confirmation.

Quick start

You need Go 1.24.2 or newer, Git, an interactive terminal, and your chosen agent CLI installed and authenticated. Stvena uses Unix PTYs and process groups; macOS and Linux are the intended platforms. Native Windows is not supported.

go install github.com/nccapo/stvena/cmd/stvena@latest
cd /path/to/your/project
stvena                    # Starts Codex
stvena claude             # Starts Claude Code

Make sure Go's binary directory (go env GOBIN, or $(go env GOPATH)/bin when GOBIN is empty) is on your PATH.

Or build from source:

git clone https://github.com/nccapo/stvena.git
cd stvena
go build -o bin/stvena ./cmd/stvena
./bin/stvena --help

Launch Stvena inside the Git project you want to work on. You can pass an agent command and its arguments after --, or reopen a saved review:

stvena -- codex --model YOUR_MODEL
stvena review
stvena sessions
stvena review --session ID

Reopening a review compares a saved baseline with today's workspace; it does not resume an agent conversation. Other commands can run in the agent pane, but direct selection paste is supported for Codex and Claude Code.

A typical workflow

1. Start stvena in your project and give the agent a task.
2. Press Ctrl-G to focus review. Open a changed file, or press 3 to browse the project. Press v to switch between a diff and the full file.
3. Drag over code and press b to paste it into the agent's input. Add your request and submit it in the CLI. Use x to collect multiple selections and B to open the context tray.
4. Press t to run a check such as go test ./.... Open results with T, then o for recognized problem locations.
5. Mark a file reviewed with Space and move to the next unreviewed file with N. In Workspace view, S stages or unstages the selected file.

Key	Action
Ctrl-G	Switch between agent and review
Ctrl-Q	Quit Stvena and stop the agent
1 / 2 / 3	Session changes / workspace changes / project files
Enter / f	Open file / return to file browser
v	Toggle diff and full-file view
Drag / V	Select code with mouse / keyboard
b / x / B	Paste selection / collect selection / open context
P	Pin the displayed version or resume live updates
Space / N	Mark file reviewed / next unreviewed file
t / T	Run a check / inspect results
a / ?	Actions menu / keyboard help

Review shortcuts apply when review has focus. Ctrl-C keeps the agent's native interrupt behavior. Review remains open after the agent exits; q closes it. See the complete user guide for comments, hunk staging, search, clipboard tools, and every shortcut.

Privacy and local data

Stvena does not require its own API key or account. It launches the agent CLI you already use with your environment and credentials. Your chosen agent's network access and data handling still apply.

• Review metadata, comments, snippets, draft requests, preferences, and check output are stored under your OS cache directory in stvena/<repository hash>.
• Captured code is retained in local Git objects under refs/stvena/sessions/* and refs/stvena/reviews/*. Use normal branch pushes; a mirror push can also publish these private refs.
• Capture respects Git ignore rules for untracked files. Already tracked files are captured even if subsequently ignored. Put credentials outside Git and inspect your index before committing.
• Selected code is pasted only when requested; Stvena does not press Enter to submit it. Drafts can include absolute paths and captured source.
• Check commands run with your user permissions and inherited environment. The temporary checkout is not a sandbox. Run commands you trust.

Retained snapshots do not expire automatically. Use one Stvena process per repository to avoid competing writes to saved review state. The storage and limits guide describes capture behavior and size limits.

Development and contributions

Bug reports, focused pull requests, and usability feedback are welcome. Read CONTRIBUTING.md for setup, checks, and what to include in a report. For sensitive findings, see SECURITY.md.

go test ./...
go test -race ./...
go vet ./...
go build ./...

Package	Responsibility
cmd/stvena	Command entry point
internal/app	Agent lifecycle, event loop, input, and actions
internal/diffview	Git collection, captured content, and staging
internal/session	Snapshot capture, retained refs, and session storage
internal/review	Navigation, selections, review marks, and feedback
internal/checks	Check execution, bounded logs, and problem locations
internal/ui	Terminal layout, code rendering, and controls

The product direction and research notes describe ideas and tradeoffs; they are dated planning documents, not a promise of supported features.

License

MIT © 2026 Stvena contributors.

Stvena is an independent project, unaffiliated with OpenAI or Anthropic.