Skip to content
artelov0.1pricing

$ npx artelo init

Claude Code,Codex,Gemini CLI.One dev team.

Artelo lives in your repo. It cuts a brief into small tasks, hands them to the agents you already pay for and runs them side by side. Nothing merges until lint, types, tests and the build pass. You sign off twice: on the spec, and on the preview.

  • ✓ runs locally
  • ✓ uses your subscriptions
  • ✓ full source
  • ✓ no token markup
[1:why]

$ artelo doctor

Why agent coding falls apart on real projects.

  • ⚠ context driftOne long chat. By task twelve the agent has forgotten the spec.
  • ⚠ false doneThe agent says it’s finished. The build and the linter disagree.
  • ⚠ one at a timeThree agents installed, one of them working, you babysitting it.
  • ⚠ blank promptEvery client project starts from zero. Again.

✓ Artelo fixes this with small tasks, parallel agents, hard gates and recipes.

[2:how]

$ artelo --help

From a brief to a deployed project.

Commands

artelo init
Detect your agents and add the harness to this repo.
artelo new <recipe> "<brief>"
The planner writes a spec with pages, features and acceptance criteria. You approve it.
artelo run
Split the spec into tasks, run agents in parallel worktrees, enforce the gates.
artelo studio
Open the local dashboard: task graph, live logs, gate reports.
artelo approve <checkpoint>
Sign off the spec before building and the preview before shipping.
artelo deploy
Ship to Vercel and get the URL.

Human checkpoints: new (approve the spec) and approve (approve the preview). Everything between runs without you.

What lands in your repo

.artelo/
├── config.yaml # which agent plays which role, budgets, deploy target
├── roles/ # planner, frontend, backend, qa, reviewer. Edit any prompt
├── recipes/ # landing, telegram-bot, saas-mvp, or your own
├── gates.yaml # lint, types, tests, build, lighthouse, a11y thresholds
├── decisions.md# shared memory, so agents stop re-deciding the stack
└── runs/ # logs, gate reports and screenshots for every run

$ artelo recipe list

RecipeStatusBuilds
landing● at launchcopy, design tokens, sections, lead form, seo, deploy
custom● at launchyour own recipe: yaml + prompts + scaffold + gates
telegram-bot○ in developmentbooking, reminders, payments, admin
saas-mvp○ in developmentauth, postgres, stripe, admin panel
[3:agents]

$ artelo agents

Bring the agents you already pay for.

Artelo doesn’t replace your coding agents. It gives them roles, small tasks and a quality bar. Mix them per role, and the reviewer is never the agent that wrote the code.

AgentSupportGood atRuns on
claude-code mascotclaude-code● at launchplanner · frontend · reviewsubscription or API key
codex mascotcodex● at launchbackend · testssubscription or API key
gemini-cli mascotgemini-cli● at launchcopy · docs · seoAPI key
cursor-cli○ planned——
aider○ planned——
config.yaml
# .artelo/config.yaml
executors:
planner: claude-code
frontend: claude-code
backend: codex
copy: gemini-cli
reviewer: claude-code # never reviews its own task
budget:
max_minutes: 120
max_retries: 2
deploy: vercel

$ artelo studio

→ http://localhost:4317

A local web dashboard for the same run: task graph, live log per agent, gate reports with screenshots, and buttons for the two human checkpoints.

studio · task graph
[T0 scaffold]─┬─[T1 tokens ✓]──┬─[T3 hero ✓]─────┐
│ ├─[T4 pricing ▶]──┤
└─[T2 copy ✓]────┴─[T6 seo ✓]──────┤
[T5 form api · retry]────────────────────────────┴─[T7 e2e]──▶ review
[ approve preview ] unlocks after review passes
[4:pricing]

$ artelo license --plans

Founding price, until launch day.

solo

$149was $249

one-time · founding price

  • + full source code
  • + all recipes + studio
  • + 12 months of updates
  • + private community
Get Solo
team · for agencies

$499was $799

one-time · founding price

  • + everything in solo
  • + up to 5 developers
  • + white-label recipes
  • + custom recipe template
  • + priority support
Get Team
setup

from$2,500

fixed scope, quoted after a call

  • + installed on your stack
  • + one custom recipe built for you
  • + team onboarding session
Talk to us
  • # Founding members get early access before the public launch.
  • # 14-day refund, no questions asked.
  • # Agents run on your own subscriptions or keys. We never resell tokens.

$ artelo reserve

Reserve the founding price.

Planplan

Just your email. No payment now. You pay the founding price when early access opens.

[5:faq]

$ man artelo

Before you ask.

Do I need all three agents?

No. One is enough: every role can run on Claude Code, for example. More agents means more parallel work and a reviewer that isn’t the author.

Does it work with my Claude or ChatGPT subscription?

Artelo drives the agent CLIs you already have installed and logged in, so they run on whatever plan you use with them. Check your plan’s usage limits before running large jobs.

What if I have no agents installed?

There is a built-in fallback executor on the Claude Agent SDK that runs with an Anthropic API key.

Does it work on existing projects?

At launch, recipes start new projects. Adding features to existing repos is on the roadmap.

Is it open source?

You get the full source code under a commercial license. Read it, change it, extend it. Just don’t resell it.

Can I write my own recipes?

Yes. A recipe is a spec template, a task graph, role prompts, a scaffold and gate thresholds. Package the process you already sell and reuse it on every client.

When do I get access?

Founding members get early access before the public launch. If it’s not for you within 14 days, you get a full refund.