$ handoff
Hand tasks from one agent to another without losing context.
Keep the brief, current repo state, and task intent intact as work moves between agents instead of restarting the conversation every time a different tool takes over.
Flow
$ scope
Derive tasks directly from scope.
Start from the shape of the work itself and let Nora break that into actionable units instead of manually rewriting the same plan for every agent session.
Planning
$ skills
Attach the right skill set to the run.
Use a skill manager to bring specialized instructions and workflows into the session without bloating the default agent prompt.
Extensions
$ worktrees
Give every agent its own isolated worktree.
Keep experiments, edits, and reviews separate by default so parallel work does not turn the main branch into a collision zone.
Repo isolation
$ repo ops
Search files, edit files, and review diffs in one surface.
Move from search to edit to Git review without leaving the workspace. Nora is designed to keep the operational loop tight around the actual repository.
Repo tools
$ screenshots
Paste screenshots into terminal-based agents.
Bring visual context directly into CLI agent workflows. Nora lets you paste screenshots into terminal-based agents, which is not something they support natively on their own.
Visual context
$ ide handoff
Hand work back to the IDE you already prefer.
Use Nora as the operating layer, then jump into your preferred editor for deeper inspection, local debugging, or final polish without losing the thread of the work.
Preferred editors
$ remote
Manage SSH-mounted repos like local projects.
Remote work should feel first-class. Nora is being shaped around SSH mount management so remote repositories can be operated on with the same clarity as local ones.
Remote mode
$ integrations
Connect the delivery layer, not just the editor.
Source control and deployment need to stay in the same flow. GitHub and Vercel integrations are part of the working surface, not an afterthought.
Connected stack
$ visibility
See the entire operation in a multi-agent grid view.
Track active agents, task status, ownership, and repo progress in a layout that is meant for operating a system, not just reading a transcript.
Control plane
$ faq
Questions visitors usually ask first.
A quick overview of what Nora does, who it is for, and how it fits into an agent-driven development workflow.
What is Nora?+
Nora is a CLI-first workspace for running agentic development workflows with local agents, isolated worktrees, and explicit operator control.
Which coding agents does Nora work with?+
The current product direction is built around tools like Claude Code, Codex, Gemini, and Cursor, with the goal of giving them a shared operational workspace instead of separate silos.
Does Nora run agents locally?+
Yes. Nora is designed around local-first execution so you can operate agents against your repository with direct visibility into files, diffs, and task ownership.
Why use isolated worktrees?+
Separate worktrees let multiple agents explore, edit, and review in parallel without stepping on the same branch, which makes merges and human approvals much cleaner.