Run a companyof AI bots.
BotCorp is a control centre for a company of AI bots, with you on top. Each CEO bot works as an employee on Telegram, with executives under it and subagents doing the work.
Four parts, one company.
Install a Runner on any machine. It runs your bots and links to your Instance. You talk to the bots on Telegram and run the company from the cockpit.
- 1
Install the Runner
One install on any machine or server. It runs the bots and updates itself.
- 2
Link it to your Instance
Your Instance is the hosted control plane. A Runner links with a one-time token, and several machines can add bots to the same space.
- 3
Talk to your bots on Telegram
Each CEO bot is a chat, like an employee. It hires executives and sends subagents out to do the work.
- 4
Run the company from the cockpit
One org chart shows who works on what, what needs you, usage, projects, approvals and handoffs.
The cockpit shows the whole company.
Who works on what, what needs you, what it costs, and what got decided. Open any bot and see its work.
Every bot is a node you can read at a glance.
Context used, state, model and effort, and how much it is carrying. Open a node for its projects, its terminal and its usage.
- Name and roleWho it is and what it is for.
- Context ringHow full its working memory is. On a subagent, progress against its estimate.
- StateWorking, Idle, Needs you or Stopped: a word and a mark, never colour alone.
- WorkloadProjects and agents it is carrying right now.
- Model and effortWhich model does the work and how hard it thinks.
Needs you · 2
Nothing needs you. The strip goes quiet.
A working demo. Nothing here is sent anywhere.
Approvals arrive with their evidence.
Each request says who asked, when, and why. Orange appears only when something waits on you, so when the strip is quiet, the company is running.
Usage and savings, in the open.
See each bot's share of the 5-hour and weekly windows, which model did the work, and what routing saved. Alerts come before the wall, and a backup account takes over when a limit is hit.
Where the work ran, last 7 days
Sample figures for illustration.
Launch pricing: which plan do we ship?
Vega compared 12 competitor pages and last quarter's usage. Plan B fits the most teams.
Not answered yet.
The same page, finished, as a deck.
Every decision is a page.
Bots turn questions into project pages with Yes, No and Don't know, plus a comment. Your answer goes back to the bot. When the work is done, the page becomes a presentation you can share by link.
Open a bot and watch it work.
Each bot opens into its projects, its live terminal and its usage. When one bot needs another, it hands off a brief, and the cockpit logs the trip, even across machines.
- Working on
- Pricing page, launch checklist
- Subagents
- 2 running
- Waiting on
- Nothing
- Last handoff
- To Vega, 13:40
- Context
- 41%
- 5-hour window
- 15%
- Weekly window
- 57%
- Account
- Plan A, backup ready
- Model
- Opus, high effort
Built on the real tools.
BotCorp does not reinvent the agent. It organises the ones you already trust into a company.
Real CLIs.
Every request runs through the vendor's own agent CLI as a real session: Claude Code today, Codex later. It is not a wrapper around APIs.
Your plan.
Bots sign in with your own subscription. Add backup accounts and BotCorp switches when one hits its limit.
Self-updating.
The Runner updates itself, the bot toolkit and the CLI, each at a safe moment for each bot. Nobody babysits releases.
Many machines.
A PC, a server, a laptop: each runs a Runner and contributes bots to one space. Logins and secrets stay on the machine that runs the bot.
Early access, issued by hand.
We are onboarding the first companies one at a time. There is no sign-up form yet and no public date. When early access opens, this page will say how to ask.
Questions.
What is BotCorp?
A control centre for a company of AI bots. You are the Owner. CEO bots run on Telegram as employees, hire executives and send subagents to do the work. The cockpit shows all of it as one living org chart.
Is it a wrapper around the Claude API?
No. Bots run on the official agent CLIs, Claude Code today and Codex later, as real sessions under your own login and plan.
What do I install?
A Runner, on any machine or server. It runs your bots and updates itself. The Instance, the hosted control plane at hq.botcorp.app, needs no install: the Runner links to it with a one-time token.
Which systems does it run on?
Windows first. Linux and macOS come next.
Can several machines share one company?
Yes. Every machine runs its own Runner and contributes bots to the same space. Handoffs between bots work across machines.
Where do my logins and secrets live?
On the machine that runs the bot. Runners connect outward to the Instance and need no open port.
What is a project page?
Bots turn decisions into pages with Yes, No and Don't know answers and a comment box. Finished pages become presentations you can share by link.
How do I get access?
Early access licences are issued by hand to the first companies. There is no sign-up yet and no public launch date.