AI Agent Orchestration

10× more tasks.
Same team.

Run 5, 10, 20 AI agents in parallel — each on its own task, its own branch, in an isolated container. You stay in control. Every decision is yours.

US-142 coding
🟢 auto
US-187 review
🟡 checkpoint
US-203 coding
🟢 auto
US-211 done
merged
US-142 · feat: quiz validation layer US-187 · chore: schema migration ready for review US-203 · style: dark mode token update US-211 · merged to master ✓ US-142 · feat: quiz validation layer US-187 · chore: schema migration ready for review US-203 · style: dark mode token update US-211 · merged to master ✓

Parallel agents without
orchestration is chaos.

You've tried running multiple Claude Code sessions. They collide — overwriting each other's changes, rebuilding shared code, stepping on each other in the same repo.

01
Agents collide
Two agents touch the same shared package simultaneously. One overwrites the other. Neither knows it happened.
02
No visibility
Five terminal windows open. You don't know which one is working, stuck, or silently broken until you check manually.
03
Merge anxiety
Agent finished — but you have no idea what it changed or how it affects the rest of the codebase. Every merge is a gamble.

From issue to merged code
without touching a terminal.

Label an issue in Linear. 10times.dev handles everything else — cloning, containerizing, running the agent, notifying you, previewing, merging.

📋
01
Create Issue
Add label "agent" in Linear
02
Auto Spawn
Clone + container + ports in ~30s
🤖
03
Agent Works
Reads TASK.md, codes, commits
🔔
04
You're Notified
Telegram + Linear status update
👁️
05
Preview
Local or remote public URL
?
06
Your Decision
Merge, reject, or give feedback
♻️
07
Cleanup
Container gone, ports freed
You are of more value
than many agents.

AI doesn't know good from mediocre. It can't feel that the UI is off by just one pixel in a way that kills conversion. It doesn't have 10 years of context about your users, your team, and your product.

With 10 agents working in parallel, your judgment — what to build, what to reject, when it's good enough — becomes the bottleneck. Your taste is the compiler. Your experience is the architecture.

"You are of more value than many agents" — Mt 10:31

Everything you need to
orchestrate at scale.

🔒
Full Isolation
Every agent runs in its own Docker container with its own Git clone, file system, port set, and zero access to your host environment. What happens in the container stays there.
~/ukryteskarby/agents/
├── US-142/ ← own clone, ports 4122–4124
├── US-187/ ← own clone, ports 4222–4224
└── US-203/ ← own clone, ports 4322–4324
👁️
Live Preview — Local & Remote
Every branch, every agent — instant preview. Local for your own validation, remote for sharing with clients, PMs, and testers. Public URL ready before the PR even exists.
Mode What you get For who
Local Docker · localhost · hot reload You, fast review
Remote Supabase branch DB + Netlify deploy · public URL · auto TTL 24h Client, tester, PM
🔌
Global Port Registry
100 slots shared across all projects. Round-robin allocation, zero collisions.
4122
4222
4322
4422
4522
9102
9202
9302
9402
9502
📌
Linear as Source of Truth
No local state files. No lockfiles. Agent status lives in Linear issue comments. Dispatcher polls every 60s. Agent lifecycle mirrors issue lifecycle.
📱
Telegram Notifications
Dedicated thread per task. Every commit, every status change, every "ready for review" — straight to your phone. No dashboards required.
🔗
Integrations
Built-in connectors for the tools you already use. Plugin system for adding your own.
Linear
GitHub
Supabase
Netlify
Telegram
Sentry
🚨
Sentry → Auto Fix Pipeline
Production alert fires in Sentry → automatic Linear issue created → agent spawns, reads the stack trace, proposes a fix → PR lands in In Review. From production error to ready-to-merge patch — without a single manual step.

Agents don't stop.
You stay informed.

Two-tier commit classification means agents never block on a review. They mark what needs your attention and keep moving. You catch up asynchronously.

🟢 AUTO
Refactoring, styling, new files, obvious bugfixes Agent continues without waiting. No review needed.
🟡 CHECKPOINT
API changes, schema migrations, shared packages, config Requires your review. Agent pushes, marks, moves on. You're notified.
🟢 AUTO
Component isolation, test additions, type fixes Safe to ship. Auto-classified.
🟡 CHECKPOINT
New migration file: add_quiz_results_table.sql Full description: WHAT + WHY + IMPACT + SQL attached. You decide when to run.
Database rule Agents NEVER run migrations. They create SQL files in supabase/migrations/ and mark 🟡. You run them manually on stage, then prod. Always.
Conflict rule Agents rebase on master every 3–5 subtasks. Push after every subtask. Never force-push without --force-with-lease. Never touch another agent's code.

Designed to grow with you.

100
concurrent agents
100 port slots × 6 ports each. Shared across all your projects.
0
extra infra
State lives in JSON files. No database, no external service, no ops overhead.
24h
preview TTL
Remote previews auto-expire. No forgotten Netlify deploys eating your quota.
projects
One 10times.dev instance. Multiple repos, Linear workspaces, Supabase projects.

"You are of more value
than many agents."

A talk about what nobody in the AI hype cycle wants to admit: more agents means more human judgment, not less. Your taste, context, and intuition become the system's only meaningful bottleneck.

Live demo. Real repo. Real agents running in parallel. No slides pretending this works — it works on stage.

50 MIN Full format — 6 blocks + live demo + Q&A
25 MIN Condensed — one demo, one thesis
WORKSHOP 4–8h — attendees build on their own repo
Target conferences
BoilingFrogs WarsawJS 4Developers Infoshare Confitura Segfault JSConf AI Engineer Summit LeadDev
Speaker

Former academic lecturer. Solo developer. Founder of UkryteSkarby.pl. Building in public with Claude Code since it shipped. This talk is live documentation of a real system running a real product.

Early Access

Run your first
10 agents today.

10times.dev is in private early access. Join the list and get the repo, the CLAUDE_GLOBAL.md, and a walkthrough of the full setup.

No pitch. You'll get a GitHub link and a setup guide.