Releavo writes the code

Switch coding on and Releavo builds a story itself, in its own dev box, and opens a draft pull request under your name.

With coding switched on, a developer or the tech lead presses Releavo builds it on a story. Releavo writes the code in the project's own dev box, runs the tests, and opens a draft pull request on a branch of its own. The team reviews and merges it like any other.

Switch it on

The tech lead, the PM or a project admin opens the Coding tab and picks:

• the repository, from a connected GitHub, GitLab or Azure DevOps connector;
• the base branch (empty: the repository's default);
• the dev box size: Small (4 shared CPUs, 2 GB), Medium (2 CPUs, 4 GB) or Large (4 CPUs, 8 GB).

Until then Releavo never writes to your repositories.

Build a story

1. On a story, Releavo builds it. The dialog shows the branch it will make (releavo/VD-35-cart-tiers), a box for anything it should know beyond the story, and a credit limit.
2. It reads the story, its epic and the architecture, then the repository's own guidance (CLAUDE.md, CONTRIBUTING.md, the README), and builds what the story asks.
3. Watch it on the story card: each step as it happens. If the story is unclear in a way that matters, it asks you there and in your chat, and waits up to 30 minutes for the answer.
4. Send it instructions while it works, or Stop: what it did so far is kept.
5. It opens a draft pull request. After that, Continue gives it new instructions, and it carries on from the same branch.

Who it says wrote it

Every commit is authored by the person it was working for (whoever pressed Releavo builds it, or Continue), with Co-authored-by: Releavo on each one, and the pull request says it came from Releavo and links back to the story.

What it never does

• Push to any branch but its own releavo/ ones, merge, or force-push.
• Change its own rules: the repository's Claude settings aren't loaded, and it runs without your repository's credentials (Releavo pushes its branch for it).

A merged or closed pull request ends the session; pressing Releavo builds it again starts a new branch.

Credits

Its AI usage and the dev box's running time come from the workspace's credits: about 5, 25 or 50 credits an hour for a small, medium or large box, which switches itself off when nothing runs. Each session stops at its credit limit (1,500 by default; raise it and Continue). How many sessions run at once depends on the plan: 1 on Free, 2 on Team, 5 on Pro; more wait their turn.