0001
Point it at the repo
Kelt Forge reads the files a request actually touches, not just the one you had open, and works from your project's existing structure and conventions instead of guessing at them.
agentic software engineering
Describe what to build.Review every change.
Kelt Forge turns plain-language requests into planned, working software. Review the project files, saved changes, and live preview before anything ships.
Real project files. Real Git commits. Real Vercel previews.
▾
▾
to continue
See the loopclick the water to re-weave
project files loaded·plan prepared·changes saved·build verified·preview ready·approval required·git commit saved·secrets protected·project brain updated·project files loaded·plan prepared·changes saved·build verified·preview ready·approval required·git commit saved·secrets protected·project brain updated·
The loop
A ticket goes in.
A reviewable change comes out.
0010
It plans in the open
Before a single line changes you get an ordered plan: the files it will touch, what it will add, what it will delete, and what it is unsure about.
0011
It writes and runs the tests
Kelt Forge makes the edits directly in your repository, runs your suite, and reads the failures — iterating where it can, or stopping and telling you exactly where it got stuck.
0100
You review a real diff
The output is a real commit in your own repository, with a summary of what changed and why. Review it in your own git host, on your own terms.
Engine
Built like infrastructure,
not like a chat window
Whole-repo context
Kelt Forge searches and reads across your repository before it edits — not just the file you had open — so a rename is more likely to reach the call sites, the tests, and the docs too.
Works on your branch
Point it at a repository and it commits directly to your checked-out branch, then pushes to your own remote — no fork, no hidden service holding your code.
Your conventions win
It reads your linter, your formatter, and the code around it. Output looks like the rest of your codebase, not like a tutorial.
Scoped to your project
File access and shell commands are enforced to stay inside the project's own directory — a run can't reach outside the repository it's working in. It executes on Kelt Forge's own infrastructure, not your machine.
Reversible by design
Nothing is force-pushed and nothing is merged without you. Every change is a real commit in your repository — reviewed and reverted the same way you'd handle any other commit.
Your keys, your code
Secrets are stored server-side with vault-backed protection, never in your codebase, and nothing reaches your main branch without your approval.
Verified, not vibed
It has to prove the change
before you ever see it
An agent that writes code without running it is a suggestion engine. Kelt Forge runs your tests, reads the stack traces, and tells you what it could and could not verify — and nothing reaches your main branch without your approval.
- Runs your suite, not a synthetic one
- Stops instead of guessing
- Reports what it could not verify
- Attaches the full command log
run · keltforge-482saved
$ keltforge run "extract billing into its own module"
reading relevant project files …
preparing implementation plan → 6 edits, 2 new files, 1 deletion
updating project files …
running the configured build …
build clean
saving git commit …
commit saved
waiting for approval before main
Commands scoped to the project directoryenforced
Runs with a bounded turn limitevery run
Install and build timeouts enforcedevery run
Workspace disk ceiling enforced500MB default
Agent roles live today1 of 8 planned
The deliverable
No black box.
Just a real commit.
Every task ends the same way it would with a human engineer: a commit, a diff, and a description of what changed and why — reviewable in your own git host.
src/billing/charge.ts
1 @@ -1,14 +1,17 @@ src/billing/charge.ts2−import { stripe } from "../vendor/stripe";3+import { gateway } from "./gateway";4+import { PaymentError } from "./errors";56 export async function charge(order: Order): Promise<Receipt> {7− const res = await stripe.charges.create({8− amount: order.total * 100,9− currency: "usd",10− });11− return { id: res.id, paid: res.paid };12+ const res = await gateway.charge({13+ amountCents: toCents(order.total),14+ currency: order.currency,15+ idempotencyKey: order.id,16+ });17+18+ if (!res.ok) throw new PaymentError(res.reason, order.id);19+ return { id: res.reference, paid: true };20 }21▌
files
6
added
+128
removed
−94
status
Saved
Start
Your backlog is not a mystery.
It is just unassigned.
Describe the change in a sentence, point Kelt Forge at a repository — or let it start a fresh one — and read the plan before anything runs. It works inside the version control and CI you already have.
80
max turns per run
0
merges without your approval
1
agent role live today
100%
of commands scoped to your project