Simple and Developer Mode
Two views of the same controlled run
Interface mode is a per-user preference. A founder supervises agent work in plain language: plans, verdicts, decisions. An engineer sees branches, diffs, logs, and tokens. Both modes call the same server actions on the same data, under the same rules.
The founder view
Simple Mode is supervision without translation overhead: everything you need to approve, judge, and ship agent work, in plain language.
Plans in plain language
Before a run executes, Simple Mode shows what the agent proposes to do and states plainly that nothing touches the project until you approve. The approval is yours either way.
Verdicts you can act on
The independent review reads as what changed, whether it meets the request, and a recommendation. No diff literacy required to make a sound call.
Decisions, not ceremonies
Approve the plan, read the verdict, decide the merge. The vocabulary is plain, but the buttons drive the same server actions Developer Mode does.
The engineer view
Developer Mode is a conventional Git host with the run machinery exposed. One toggle away, always.
Branches and diffs
The same run shows its keelson-ai/* branch, the full diff, and the review request, exactly as a conventional Git host would.
Logs and provenance
The run timeline, provider and model stamps, and the raw review report. Nothing is summarized away.
Token-level accounting
Metered input and output tokens per run, from the same usage records that drive workspace metering.
How it behaves in practice
Progressive learning
Every plain-language label carries the real Git term and a tooltip explanation. People absorb the vocabulary from doing the work.
One-click rollback
“Undo to an earlier point” creates a new saved change (a revert) that restores the project. History is never rewritten and nothing is ever lost.
Plain-language merge conflicts
A conflict is presented as “overlapping edits”: two versions changed the same lines, and the interface walks you through choosing which edits to keep.
The vocabulary, translated
Simple Mode never hides Git: every plain-language label shows the real term alongside. This is the exact mapping the product uses, rendered from the same configuration file that drives the interface.
| Plain language | Git term | What it means |
|---|---|---|
| Save changes | Commit | A commit is a saved snapshot of your project at a point in time. You can always come back to it. |
| Create a separate version | Branch | A branch is a parallel copy of the project where you can work without affecting the main version. |
| Request a review | Pull request | A pull request asks teammates to review your changes before they join the main version. |
| Combine versions | Merge | Merging brings the changes from one version into another. |
| Download project | Clone | Cloning downloads a full copy of the project to your computer, still connected to the shared one. |
| Project history | Commit history | Every saved change, who made it, and when. Nothing is ever lost. |
| Upload your changes | Push | Pushing sends the changes saved on your computer up to the shared project. |
| What changed | Diff | A side-by-side comparison showing exactly which lines were added or removed. |
| Undo to an earlier point | Revert | Creates a new saved change that restores the project to how it was before. |
| Project | Repository | A repository holds your project's files and their entire history. |
| Overlapping edits | Merge conflict | Two versions changed the same lines. Someone needs to choose which edits to keep, and we'll walk you through it. |
11 terms, rendered directly from the shared terminology configuration.
One run, two readers
Interface mode is a per-user preference, not a workspace setting. Your engineer sees a conventional Git host; your cofounder sees plain language. Branch protection, permissions, and history are identical in both modes.