Free while we're in early access
No card, no trial clock. The limits below are the ones the server enforces, and the app shows you the same numbers.
Early access
The whole product while we're in early access: the editor, the hosted Claude agent on our key, and the iPhone companion.
- Native macOS editor built on VS Code
- Hosted Claude agent — no key to bring, no card to add
- Daily limits published below and metered server-side
- iPhone companion to watch and steer runs
- Support answered by a person
Pro
When paid plans arrive, the price, the limits and the date appear here and in the changelog before a single invoice. Early-access accounts get the transition terms in writing, with an end date.
- Price and limits published before billing starts
- Self-service cancellation; statutory withdrawal rights honored
- No "unlimited" unless it is
Teams
Shared billing, seats and admin controls aren't built yet. If you'd run Celiador for a team, tell us what you'd need and we'll say plainly what exists.
- Nothing to buy today
- Your requirements shape what we build first
Early-access limits, per account
Read live from the same endpoint the app uses, so this page can't drift from what you're actually metered against. Why we publish them.
| Agent requests per minute | 30 | rolling window |
| Concurrent agent requests | 2 | at any moment |
| Agent tasks running at once | 3 | queued issues, each in its own worktree |
| Agent requests per day | 500 | UTC day |
| Input tokens per day | 5,000,000 | UTC day |
| Output tokens per day | 300,000 | UTC day |
| Model | claude-opus-4-8 | |
Daily budgets reset at 00:00 UTC; the per-minute window and concurrency are instantaneous. The model is chosen server-side; clients can't pick it. The numbers above are read live from celiador.ai/api/limits and are the ones the server enforces.
Pricing questions
Celiador turns GitHub issues into pull requests. You label an issue celiador; an agent runs it on your Mac in its own git worktree, comments on the issue, and opens a pull request that closes it. You review and merge from your phone or from the editor's Agents view. The agent is Claude, run through our server on our key.
No. The Celiador editor, a fork of VS Code, has the loop built in and is the nicest place to watch runs. If you want to keep VS Code or Cursor, install the Celiador Remote extension: same loop, same account, same phone. Cloud runs for when your Mac is off are being built and will need the Celiador GitHub App on the repository.
Routine commands run on their own. A risky command or a question shows up under Needs you on the phone and in the Agents view, with Allow and Deny, and the run waits. Posting the same question on the issue, so you can answer by replying, is being built.
Yes, as early access. The editor is a signed, notarized macOS download that updates itself, with Linux x64 packages too; Celiador Remote is on Open VSX; the iPhone app is on TestFlight by invite until the public link is on the download page.
Runners: the Celiador editor on macOS (Apple Silicon) and Linux x64, or any VS Code or Cursor install with Celiador Remote. Review: iPhone, or the Agents view in the editor. A Windows build of the editor is on the roadmap; tell us on the download page if you need it.
Nothing during early access. The hosted agent runs on our key with per-account limits that are published on the pricing page and enforced by the server, and the app shows you the same numbers. Paid plans will be announced with a date before anyone is billed.
Your code stays yours. Runs happen on your machine, in a worktree of your own clone. It is never used to train models. No client holds a model key; the agent's requests go through our server, which holds the key, and nothing is indexed server-side.