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.
Korus
v0.25
Preserve the active session if the backend reconnects.
⌘Codex
I found the restore race. I’m keeping the selected session visible while the backend snapshot catches up.
✓Explored session restore flow
✓Edited 4 files
Running focused tests
Ask for follow-up changes ↑
4 sessions active
Agents do the work. You guide it forward.
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.
Mission / Add team invitationsIn progress
✓RequirementsApproved
✓TicketsReady to build
⑂ImplementationWorking
◌ReviewUp next
↗ShipWhen ready
✓Requirements & ticketsAvailable
⑂Code changesIn progress
✓Scope approved · implementation underway
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 / Start where you are
An idea. An issue.
Work already in motion.
Talk through an idea in Quick Chat, pick up a GitHub issue, or jump into an existing repository. Use a Mission for a multi-stage change or work directly with an agent for a focused task.
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.
⌕ Search open issues
#286Preserve the active session after reconnectbug
#281Improve onboarding repository pickerui
#275Show unread state on background sessionsux
ISSUE #286Where should this work happen?
Use this session
Best for follow-ups
Continue in the current folder and branch with its existing context.
New isolated session
Best for parallel work
Create a dedicated branch and worktree so this task can run independently.
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
Code review
feature/session-restore
Round 1
3 findings
Choose what to fix
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.
Codex, Claude Code—or both.
Choose the engine for each agent. Keep their work together in one workspace, across local repositories and remote teams.
Think through the system together.
Create and refine diagrams beside the conversation. Keep the design visible as your understanding evolves.
Give the next piece of work its own space.
Agents can share context and propose work in a dedicated worktree. Run local teams or connect remote teams over SSH, keeping each agent's workspace and progress in view.
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. Available for macOS on Apple silicon, with experimental Linux x64 support.
Download for macOS No Korus subscription or per-agent fee. Provider subscriptions and API usage are separate.