Features

The loop, piece by piece.

A GitHub issue goes in, a pull request comes out. Here is each part, and which parts are still being built.

acme/storefront · issue #142

Add Apple Pay to the checkout flowceliador

Use the existing ApplePay helper in pay/. Do not touch the cart.

celiadorapp1 min

Picked up. Running on stefan's Mac on branch celiador/142-apple-pay.

celiadorapp9 min

Opened pull request #143, which closes this issue.

9:41●●●

Ready for review

acme/storefront · #143

Add Apple Pay to the checkout flow

Added an ApplePay.authorize call in checkout.ts and wired the token into capture(). Lint and tests pass locally.

2 files+41−3

Follow-upApprove and merge

Running

#145 Rename the billing module

The loop

Label a GitHub issue celiador. An agent picks it up on your Mac, works in its own git worktree so your checkout is untouched, and opens a pull request that closes the issue.

Review from your phone

Celiador for iPhone shows what the agent did, the diff, and what needs you. Send a follow-up, allow or deny a risky command, then approve and merge. The editor's Agents view shows the same runs.

Your runner, your choice

Run it in the Celiador editor, or keep VS Code or Cursor and install the Celiador Remote extension. Same loop, same account, same phone.

comingCloud runs for when your Mac is off. They need the Celiador GitHub App on the repository.

GitHub is the cockpit

Every run narrates itself on the issue: a comment when it is picked up and on which branch, and the pull request link when it is done. Your team sees the work where they already look.

comingThe agent's plan and its questions posted on the issue, answered by replying there.

Every PR explains itself

The pull request says what the agent did and closes the issue it came from, so review starts from the agent's own account of the change.

comingA self-review section in every PR, per-run cost on the PR and on the card, and failed CI checks fixed by the agent.

Our key, your privacy

No client holds a model key. Requests go through our server, which holds the key and meters usage with limits we publish. Your code isn't training data.

The runners

Pick where the agent runs

The loop is the same wherever it runs: a git worktree on a fresh branch, your project's own agent settings, your git identity for the push, your GitHub sign-in for the pull request. Choose the runner that fits how you work.

Celiador editor: the loop built in, with the Agents view as the cockpit for every run
VS Code or Cursor: install the Celiador Remote extension and keep your editor
Both run on your Mac; your checkout is never touched
One account across the runners and the phone

comingCloud runs for when your Mac is off. They need the Celiador GitHub App on the repository.

celiador — checkout.ts

checkout.tscart.tsx

// add Apple Pay to the checkout flow

import { ApplePay } from "./pay"

export async function checkout(cart) {

const total = sum(cart.items)

const token = await ApplePay.authorize(total)

return capture(token)

}

Celiador Agent

Add Apple Pay to checkout

Done. I added an ApplePay.authorize call to checkout.ts and wired the token into capture().

2 files · 1 diff pending review

The review

Review it where you are

Celiador for iPhone is the queue: what needs you, what is running, what is ready for review. Open a pull request to read the agent's account and the diff, send a follow-up for another turn on the same branch, and approve and merge. The editor's Agents view shows the same runs for when you are at the desk.

Allow or deny a risky command; routine ones run on their own
Answer the agent's questions from the phone
Follow-ups keep the branch and the context
Merge from the phone; the editor does it with your GitHub sign-in