Plan, delegate, report, deliver
The lead doesn't say 'done' while a specialist still owes a report. That's enforced by the platform, not left to luck.
SHIP'S LOG
Four missions your crew can run tonight.
Real jobs, start to finish, with no engineering degree required.
You say what you want, in plain words, in the web console or from Telegram, WhatsApp or Slack on your phone. Your crew splits it up, does the work, checks it, and tells you when it's actually done. Here's what that looks like.
MISSION 01
Two researchers. One answer. Zero tab-juggling.
Your lead hands the digging to two specialists at once, then merges their work into one brief.
Ask your lead agent a question that needs real research, like which of two suppliers is the better deal. It sends a researcher after each one, in parallel, each on the model that suits the job. Each writes its findings to a shared folder and reports back. Your lead waits for both, reads both, and only then sends you the answer, on Telegram if that's where you asked.
Two specialists side by side, one merged answer, delivered once, after both reported.
MISSION 02
Your inbox has a night watch now.
An agent answers on Telegram, WhatsApp or Slack around the clock, and pulls in the right colleague when it needs one.
Connect an agent to the chat app your customers or team already use. It answers what it can. When it needs something it isn't allowed to touch, it asks the colleague who is, gets the answer, posts the update to the right channel, and writes itself a to-do list so nothing falls through.
The customer-facing agent never touched the server. It asked the one who's allowed to.
Telegram, WhatsApp and Slack are built in. Discord and other chat apps come as plugins.
MISSION 03
Kick off a long job. Go live your life.
Your agent starts work on your own server, waits without burning tokens, and pings you when it's done.
Register your server, or run our tunnel on a box behind your router, so there's no port to open. Give one agent permission to use it. Ask it to run a long job and let you know. It starts the job, sets itself a reminder in case something goes quiet, and goes idle: no model calls while it waits. When the job finishes, the agent wakes up, checks the result, and messages you.
One request. A long job on your own hardware. One message when it's really done.
Agents reach only the servers you've verified and allowed. Schedules can run jobs like this on a timer, down to every 15 minutes on Solo.
MISSION 04
Ask out loud. Get it done.
Your 3D companion listens, hands the legwork to a specialist, and tells you the result in a few spoken sentences.
Open the Companion tab in the web console and just talk. She thinks visibly while the work happens. Behind her face is a full agent, so she can call a specialist, wait for the report, and then answer you out loud, with the long details left in the chat.
One question, spoken. One specialist on the web. One spoken answer, details in the chat.
Talk to her in the web console, in the voice you pick: ElevenLabs, fish.audio, Deepgram, an OpenAI-compatible vendor, or a voice plugin.
THE PATTERN
The lead doesn't say 'done' while a specialist still owes a report. That's enforced by the platform, not left to luck.
Each specialist sees only its part, on the model that fits it. Cheap and fast for searching, top-tier for thinking.
Your crew messages you on the app you use, when the work is actually finished, even hours later.
Sign up free, paste an API key, and send the first order.