Shape the work
Work through the requirements with an agent, refine the scope, and approve a plan before implementation begins.
Software engineering, orchestrated.
From idea
to delivery.
Korus orchestrates software engineering workflows through agents. Planning, implementation, review, and delivery stay connected—with you in control of the decisions that matter.
Shape the work→Build with agents→Review the results→Ship the change
01 / One connected workflow
More than a conversation.
Work that moves forward.
Software work doesn’t end when an agent answers. Missions connect requirements, tickets, implementation, and review in one workflow. Agents carry out the work; Korus coordinates its progress and handoffs, with artifacts you can inspect along the way.
Connect the stages
Let the workflow coordinate execution and handoffs. Context, progress, and artifacts stay with the work as it moves forward.
Stay in control
Inspect what agents produce, guide the next step, and make the decisions that need your judgment. Orchestrated doesn’t mean unattended.
02 / Give work its own space
Delegate the task.
Keep the context.
Turn a feature discussion into focused work. Hand it to a dedicated agent in an isolated worktree, keep iterating together, and merge the changes back when they’re ready.
The right space for the work
Continue with existing context or create an isolated worktree. Parallel work gets its own space without losing the path back.
03 / Review through delivery
Review. Refine.
Bring it home.
A first pass isn’t the finish line. Inspect findings, send selected issues back for fixes, and review again. Keep the path from implementation to a pull request or merge in the same workspace.
- Review with the current agent or an independent reviewer
- Apply selected fixes and run another review round
- Update worktree branches before merging
- Commit, push, and deliver when ready
AUTOMATIONCritical issue intakeEnabled
WHENNew GitHub issuelabel is critical
→
ROUTE TOKorus teamcreate a focused agent
RECENT RUNS#286 Session created
#274 Completed
04 / Repeatable work
Make the repeatable
automatic.
Set the criteria once. Automations watch for matching work and route it to an agent, so recurring intake doesn’t need the same manual handoff every time. Run history keeps execution visible.
Use Automations for recurring intake alongside Missions and direct repository work.05 / The workspace behind the workflow
Agents, context, and tools.
Working together.
Choose your agents, explore a design, and follow parallel work. The supporting tools are here when the workflow needs them.
See working, waiting, unread, and ready at a glance.
See progress across your teams and spot the work that needs a decision. Pick up the thread without checking every conversation.
Start with a conversation.
Leave with a project.
Explore an idea before choosing a folder. When it takes shape, ask an agent to create the project and carry your context into the work.
Think through the system together.
Create and refine diagrams beside the conversation. Keep the design visible as your understanding evolves.
Codex, Claude Code—or both.
Choose the engine for each agent. Keep their work together in one workspace, across local repositories and remote teams.
Switch sessions. The others keep their place.
The background daemon keeps turns alive, while status and unread signals make it easy to know where to return.
Reach native apps when code isn’t enough.
Opt-in Computer Use lets a session inspect and operate native applications while every action remains visible.
Free to use. Your choice of engine.
Your next idea.
All the way to delivery.
Connect Codex, Claude Code, or both. Choose your platform.
Releases on GitHub No Korus subscription or per-agent fee. Provider subscriptions and API usage are separate.