Command a fleet of AI agents from your own private cloud. Design highly customized agents specific to the ways
you work today. Power it with any model across the frontier.
A BusyBot agent is an agent you design. Choose its brain from across the frontier and hand it tools with
specific instructions. Fine-tune agents to your specific needs.
BrainMindReachGrowth
Don’t want to start from scratch? Describe the agent you need and the Builder Assistant drafts the
whole thing — role, skill, tools, knowledge — for you to accept piece by piece.
Your agent runs on the frontier you choose. GPT, Claude, Gemini or Grok power the main loop; turn thinking
from off to max; put the supporting work — planning, reflecting, extracting — on a second provider.
Model-agnostic by design, so when a better model ships, your agent upgrades in two clicks.
OpenAIAnthropicGooglexAI
main loop
thinkingofflowmediumhighmax
supporting slots · one second providerplanreplanreflectstrategyextract
Agent Mind
This is where your agent becomes yours. Give it a Role, teach it a Skill, load it with the
Context of your business and set the Format it answers in. Plain language in, a specialist out.
Rolewho it is
Skillhow it works
Contextwhat it knows
Formathow it answers
Agent Reach
Plug in 364 tools and your agent starts doing, not just saying. It sends the email, posts to the
channel, updates the CRM, files the ticket — on your own credentials, when it judges the moment is right. Snap
on a saved workflow and a whole pipeline becomes one tool; attach a knowledge base and it reads your documents
mid-run and cites them.
workflowknowledge
364 tools, every one within your agent’s reach
Lessons Learned over time
Every run teaches your agent something. It keeps a Do / Don’t list for each tool — what worked, what
didn’t, and why — and proposes sharper instructions you approve with one click. Switch growth off any time: it
stops changing, but never forgets.
Ledger · Google Sheetsrun 1 → run 40
Dobatch the rows, then one Appendrun 3
Don’tretry a 4xx — fix the range firstrun 9
Doread the header row before writingrun 17
Doname the sheet, never the indexrun 31
Workflows
Create the workflow. Schedule it, or hand it to an agent.
Drag 453 tools across a canvas and connect them. Schedule it and forget it. Automate long running
workflows across isolated compute.
453 tools in 11 categories — integrations, model calls, data transforms, files, and the core routing steps.
85 triggers — webhook, polling, manual. A webhook gives the workflow a URL; a polling trigger keeps state so nothing runs twice.
Schedules — Trial 2 at ≥ 60 min · Starter 10 at ≥ 15 min · Pro 100 at ≥ 1 min · Enterprise unlimited at ≥ 1 min. “Run now” and the scheduled fire are one code path.
Isolated by construction — each run is its own Kubernetes Job; code steps run sandboxed in V8 isolates or containers.
Credentials — AES-256-GCM encrypted at rest, never logged, checked against the owning account on every use.
Workflows as tools — an agent attaches a saved workflow and calls a whole pipeline as one step. Groups keep them organised.
PDFs, Office files, code, text, audio, video — drag them in and BusyBot turns each one into something an
agent can read, summarise and search. When a question comes up mid-run, your agent opens the actual
document, reads it whole, and tells you which document the answer came from.
Status you can watch — draft → processing → ready, with grouping, health checks and a changelog per knowledge base.
Grounded answers — the source passage is available rather than implied; the subagent is a ReAct loop with its own tools.
One workspace with every frontier model behind it. Chat with the model you want and switch mid-thread with
your context intact, or burst one prompt to all of them at once — the same models your agents choose their
brain from.
4 frontier providers · 67 models · one workspace
One thread. Any model, mid-thread.
Chat
Switch from GPT to Claude to Gemini to Grok inside one conversation and your context travels with you —
each model picks up exactly where the last one left off. Conversations, files and instructions live in
your private cloud, and Model Radar probes the providers daily so no listed model is a dead one.
YouPlan our Q1 launch for the new analytics dashboard.
GPTThree phases: a private beta in January, the public launch in February, an expansion push in March.
YouNow tighten it to one paragraph.
ClaudeJanuary proves it in beta, February launches it, March grows it — one owner per phase.
YouAdd the dates and the owners.
GeminiBeta opens Jan 12 (Priya), launch lands Feb 9 (Marcus), expansion starts Mar 16 (Dana).
YouMake it a Slack post for the team.
GrokQ1 dashboard launch: beta Jan 12, live Feb 9, expansion Mar 16 — owners tagged in the thread.
One prompt. Every model, at once.
Burst
Send one prompt and every model answers together — GPT, Claude, Gemini and Grok streaming side by side
in one place. Pick a Lite, Regular, Reasoning or Custom squad, compare the takes as they arrive and keep
the one you like best.
The apps your team already lives in, ready for your agents and workflows. Each of these works two ways:
drop it into a pipeline, or hand it to an agent that decides when to use it. Click any one to see exactly what
it can do.
Yes. An agent’s brain — the model that runs its main loop — is any catalog chat model from OpenAI, Anthropic, Google or xAI, at a thinking level you set from off to max. The loop’s supporting slots (plan, replan, reflect, strategy, extract) run on one second provider you choose, which may differ from the main loop’s. Two frontier providers, one agent.
02What happens when a provider withdraws a model?
every daydelisted
Model Radar probes all four providers’ model APIs every day, so the catalog never lists a dead model: whatever you can pick in chat, in a Burst squad or as an agent’s brain is a model that answers. The fleet at the foot of this page is that live catalog, by name.
03Can an agent run while I sleep — and who can stop it?
schedule · triggerstop
Your workflows can: a workflow runs on a schedule (Trial 2 at ≥ 60 min · Starter 10 at ≥ 15 min · Pro 100 at ≥ 1 min · Enterprise unlimited at ≥ 1 min) or from one of 85 triggers, every run an isolated Kubernetes Job, and an agent can call a saved workflow as a single tool. An agent run starts when you hand it a job; it then works on its own — plans, calls tools in batches, reflects, asks only when it needs you — and streams into the sidebar’s live-run feed, where you can stop it mid-run from anywhere. Every run is metered and credit-gated against your balance.
04Can an agent ask me before it acts?
pauseuntilanswered
Yes. Mid-run an agent may ask you a question — with choices or a short form — and pause until you answer, then carry on with your answer in hand. Before each batch of tool calls it shows a preamble of what it is about to do; after each batch it reflects and may write down a finding; it may replan. All of it streams live into the conversation.
05What does an agent carry from one run to the next?
v2 · diffapply
Lessons. Each tool keeps a Do / Don’t list of outcomes on your account — what worked, what failed and why — written by the agent in flight and by a Notekeeper after the run. A Growth Reviewer proposes new versions of the Skill and Role into a suggestion queue with evidence and a diff; you apply, edit or dismiss each one, and every version is kept — any restorable, any freezable. Training sessions let the agent practise its tools against a plan you review first. Growth off means stop changing, never forget.
06Does an agent know what day it is?
your zone
Yes. A temporal header gives every iteration of the loop the current date and time in your time zone, so “this week”, “by Friday” and “since the last run” mean what you mean, whenever the run starts.
07Where does my data live?
{you}{them}aes-256one cluster · us
In your own private workspace on BusyBot’s Kubernetes cluster in the US. Each customer’s data is isolated to its own account (hash-tag isolation); credentials for the 295 credential types are AES-256-GCM encrypted at rest, never logged, and checked against the owning account on every use; every workflow run executes as its own isolated Job on its own node pool, and code steps run sandboxed. Conversations, files and instructions stay in that workspace as you move between models.
08How does pricing work?
$tokenscomputestoragebalance
Tokens at your plan’s markup over provider list price, workflow compute by the hour beyond what your plan includes, and storage measured nightly, all settling into one credit balance. Trial is prepaid from $20 with credits good 12 months; subscriptions start at $20/month. Bring your own model keys on Starter, Pro, Enterprise.