Rules
Our standards, written once. Applied by every agent on every task.
Orkest
Harnesses it orchestrates
How it works
Every agent is configured for one job: its own rules, skills and prompts. Orkest runs them in loops and on triggers.
Role, skills, prompt and model, set per agent.
Loops run on a schedule. Triggers pick up issues from Linear.
Verification agents check every output. Not approved goes back for fixes.
What it runs
Each is a loop or a trigger with its own agents, rules and skills, running alongside your team.
Issue in, pull request out. Planned, built and verified.
Every diff reviewed for security and correctness. Findings posted inline.
Your conventions applied on every change.
Documentation updated with the code it describes.
Scheduled agents looking for performance wins.
Cleanup pull requests opened on a schedule.
Our know-how
Code standards, security and conventions from years of shipping, written into every agent. A verification agent checks each output against them.
Our standards, written once. Applied by every agent on every task.
Reusable practices per task, ours and thousands from the community.
Every plan ends with a verdict. A rejection adds fix tasks and runs again.
Your control
Automation your team can see, review and approve.
Running plans, agents at work, tokens and spend, in real time.
An isolated worktree per repo. Work lands as a pull request on a feature branch.
Any finished plan becomes a narrated video of its changes.
A blocked agent asks for help. The plan waits until you resume it.