kill9

Agent delivery workspace for software teams

Slash the process.
Ship faster.

Give kill9 a ticket. It plans the work, edits your repo, runs the checks, and brings every consequential decision back to you.

You approve the decisions. kill9 handles the process.

>curl -fsSL https://kill9.ai/install | sh
A kill9 agent session mid-fix: repository read, a one-line source change, and passing verification evidence

Prompt → repository read → reproduced failure → one-line fix → passing verification.

Watch the full tour →
Imports from
Product film

Watch the work happen.

One ticket, start to finish — in the real app, not a mockup. Watch it happen: the agent works, the process holds, the memory carries, and you decide what ships.

One ticket, followed all the way through the product.

An agent that reads your repo and fixes the code. A workflow that keeps the process honest. Project memory that carries between sessions.

Get kill9 →
01Agent session
02Workflow
03Memory
One delivery workspace

The whole loop stays inspectable.

kill9 does not hide planning, execution, context, and review behind a single progress spinner. The surfaces stay distinct so the team can understand what happened and decide what happens next.

01Agents

Specialists that use the repository, not a toy sandbox.

Route work to focused agents, inspect every tool call, and keep the parent session responsible for the final result.

Delegation · tool evidence · session lineage

Open guide →
02Workflows

A delivery process the team can inspect and change.

Define lifecycle states, ownership, required artifacts, and review gates instead of burying the process in prompts.

Stages · transitions · approval boundaries

Open guide →
03Context

Project memory that survives the next handoff.

Keep decisions, conventions, prior evidence, and repository context available without pasting the same brief into every session.

Memories · decisions · supporting evidence

Open guide →
04Review

A human-readable boundary before work moves forward.

Inspect the changed files and exact patch, then approve, revise, or reject with the evidence still attached to the work.

Focused diff · AI review · explicit approval

Open guide →
Learn by doing

Start with a real task.

The guides follow the same boundaries shown in the product film: establish context, let the agent work, inspect the evidence, and keep the final decision human.

System

Everything that keeps the loop inspectable.

A local desktop workspace, explicit workflow state, model choice, and tools you can inspect. Not an opaque queue behind a chat box.

Get Started

Start with one repo and one small task. Keep every decision visible.

Early Access·macOS / Linux · Windows soon