Coding agent
Turns a refined brief into a pull request. Lithify runs the coding agent for you — you
don't install anything or run a worker locally. When a brief is assigned to the coding agent, it
moves through working while the agent makes its changes, and lands in review when there's a PR ready for a human to look at.
What it does
- Reads the brief — title, description, type, priority and any prior attempt feedback.
- Branches your repository in an isolated workspace.
- Makes the change, runs whatever validation the project has wired up, commits the result.
- Pushes the branch and opens a pull request on GitHub or GitLab.
- Hands the brief to
reviewwith the PR link and a short summary of what it did.
You only need to point Lithify at the repo. Configure the source-code location under Project → Settings and connect a GitHub or GitLab integration with push access. Everything else — the agent, the branch, the PR — is on us.
Lifecycle
- A workflow rule assigns the brief to the coding agent.
- The brief enters
workingwhile the agent runs. - On success, the brief enters
reviewwith the PR URL recorded. - If the agent can't finish (missing context, environment failure, etc.), the brief returns to
readyand the project manager is notified.
Default workflow rule
trigger: state_enter · ready condition: type = bug action: assign → coding agent
Adjust this rule (or add more) when you want non-bug types to flow to coding too — or when you want only briefs above a certain priority to auto-route, leaving the rest for a human to send manually.
Reopen with feedback
If the first PR isn't right, leave feedback on the brief and reopen it. The next attempt starts with the prior PR URL, the agent's previous summary and your notes already in context, so it can build on (or correct) what came before instead of starting from scratch. Each attempt gets its own branch — old work is never overwritten.