Custom AI roles — the catalogue this role comes from.

Coder — Assemblable today

Works in the repository you point it at: reads the code, makes a small reviewable change on its own branch, runs the checks and hands back the diff with what it could not verify.

Build this one

Start from this role and tell the designer what changes — no need to describe it again.

Start from this role

Already know this is the one? Launch the live workspace now — it deploys immediately, to your wallet, with no review conversation.

What it does

The Coder takes a repository and a problem. It reads the repository's own README, instructions and tests before it changes a line, then locates the change: it reproduces the failing command where it can, or reads the code path and names the place the change belongs. It works on a branch of its own, makes the smallest diff that solves the stated problem, runs the checks the repository actually has, and hands back the branch with the output.

The connection is yours, not ours. You give it a repository and decide what it may do there: a deploy key lets it clone and, if you tick write access, push a branch; a fine-grained token lets it open a pull request through the GitHub API. The key or token lives inside your container at 0600 and is scoped to the repository you named. The coder does not merge, does not deploy, and does not rewrite history. It reports the branch, the commits, the checks it ran and the checks it could not run — including a native iOS build, which this Linux container cannot do.

What you get

ArtefactProduced by
Branch with a reviewable diff — the smallest change that solves the stated problemDeepSeek deepseek-v4-flash, on a branch of its own
Checks run with their real output — the commands the repository uses, and what they printedthe repository's own test command, run in the container
Pull request — a title, the change, the checks and what is unverifiedthe GitHub REST API, with your fine-grained token
Compare link — the branch pushed and ready for you to reviewgit push, when you have not issued a token
Change report — branch, commits, files, what was not run and what is needed nextDeepSeek deepseek-v4-flash
The connection itself — a deploy key or token scoped to that one repositoryconnections/github, write access only if you grant it

Nothing in this role needs a document renderer: code, tests and a pull request are text. The GitHub connection carries no per-call price and is your own account — the repository and its Actions minutes are yours. A native iOS build is not possible in a Linux container: the coder edits Swift and JavaScript sources and runs what runs on Linux, and says plainly what it could not run rather than reporting a build that did not happen.

The parts it is made of

What it costs

One supplier is attached, DeepSeek, metered at $0.00700 a call on Base, with the call counts assumed rather than observed. The GitHub connection has no published per-call price: it is your repository, and the Actions minutes are yours. This is a coding month, not a reading month — a task costs several times what a document brief costs, because the agent reads, edits and runs checks in a loop.

CallUnit priceCallsCost
DeepSeek deepseek-v4-flash — reading the repository and locating the change, fifteen a task$0.00700150$1.05000
DeepSeek deepseek-v4-flash — the edit, twenty a task$0.00700200$1.40000
DeepSeek deepseek-v4-flash — the checks and the fix loop, ten a task$0.00700100$0.70000
DeepSeek deepseek-v4-flash — the change report and the pull-request body, five a task$0.0070050$0.35000
GitHub connection — deploy key or token, repository and Actions minutesno published per-call price10 branches, 10 pull requestsnot costed
Total500 paid calls$3.50000

An illustrative month, twenty working days: ten tasks, about two a week, at fifty paid calls each — fifteen to read the repository and find the change, twenty to write it, ten for the checks and the fix loop, five for the report and the pull request. The counts are assumptions, not observations: a task in a large repository, or one that needs several failed test runs, costs more.

The arithmetic is short. 500 calls at $0.00700 is $3.50000, or $0.35 a task. At the metered ceiling of $0.00955 the month is $4.77500. The 0.50 USDC opening balance is seventy-one calls at $0.00700 — about one and a half tasks at these counts, so the first month is funded rather than free. The three ceilings stop one long agentic loop from spending the balance on its own.

The GitHub connection carries no per-call price: the repository and its Actions minutes are your own account. There are no document parts in this role, so nothing is left outside the total except the model calls themselves.

Services it buys, per call

What it refuses

Three boundaries, each one a limit the workspace enforces rather than a preference of the coder's.

It will not merge or deploy on its own. The coder pushes a branch; merging it, releasing it and deploying it are decisions that belong to you. A production restart, a migration or a deploy needs your explicit approval, not an inference from the task. That is why the deliverable is a branch and a pull request rather than a changed default branch.

It will not invent a passing check. Every claim about the change is backed by a command that ran and the output it printed. Where a check could not run — a native iOS build with no Xcode, a service the container cannot reach, a test suite the repository does not have — the report says so in those words. A green summary that no command produced is the one thing the workspace treats as a failed turn.

It will not take a credential into the repository. A deploy key or token lives in the coder's own home at 0600, never in the shared workspace tree, a commit, a log or a chat message. The workspace files are browsable by every member; the profile home is not. Access is scoped to the repository you named and can be revoked by you without involving us.

Questions

What does it cost to start?

0.50 USDC on Base, credited to your workspace as opening capital rather than a fee. At $0.00700 a call that is seventy-one calls, about one and a half tasks at the counts above — so a first month is funded, not free. The three ceilings stop a single long agentic loop from spending the balance, and the workspace records every call.

What access does it need?

A repository and one decision. A deploy key is enough to clone, and with write access, to push a branch; a fine-grained token with Contents and Pull requests is needed if you want the coder to open pull requests. You add either one yourself and can remove it in a click. It needs no fleet credential, no studio access and no account of ours.

What will it not do?

Merge to the default branch, force-push, rewrite history, deploy to production without your approval, or change a dependency or CI pipeline without agreement. It also will not run a native iOS build, because this container is Linux and has no Xcode — it edits the sources and runs the checks that run here, and names the gap.

Start

The first useful output is one small task in one repository you already know: the failing command, the file you suspect, and the branch you want it on. Start at /design?start=coder: about ten exchanges settle the repository, the access you will grant, the checks that count as done, and the ceilings. A person approves the proposal before anything is provisioned.

Build this one

Start from this role and tell the designer what changes — no need to describe it again.

Start from this role

Already know this is the one? Launch the live workspace now — it deploys immediately, to your wallet, with no review conversation.

Other roles