Theo Claw

So your workers can send email without borrowing your personal Gmail or Outlook, set up an agent inbox. Open Theo Claw from the dashboard and click Set up agent inbox. A short guided setup creates one shared inbox — every worker reuses it — with nothing to host or maintain on your side. By default your address is name@opencharts.bot (you pick the name).

Use your own domain. Want messages to come from name@yourdomain.com instead? In the setup wizard’s Domain step, add your domain and copy each DNS record into your domain host — every host and value has a one-tap copy button. Then click Check verification, or just wait: the wizard re-checks automatically until the domain flips to Verified. Once it’s verified, move the inbox onto it. A domain you add is reused across every worker.

Add a signature. Build a polished signature for free on SignForge (the Open SignForge button opens it in a new tab), paste the HTML back into the signature box, and it’s appended to everything the worker sends — with a live preview as you paste.

Prefer to send from your real mailbox instead? Switch Email delivery to your connected Gmail or Outlook at any time.

Large attachments. Files up to about 10 MB are attached directly. Bigger files are delivered as a secure download link inside the email instead — the recipient clicks through to a branded download page, and the send never fails because of file size. If the email provider hiccups on an attachment, the worker automatically retries with download links so the message still goes out.

Two-way email.When someone replies to a worker's email, the reply routes back to that worker and it answers from the same inbox. Each correspondent is a separate ongoing thread — the worker remembers the conversation, so a follow-up picks up right where it left off. Replying to the person who emailed is automatic (like texting back); emailing anyone elsestill follows the worker's approval policy.

Enable Send a text message in the worker’s Configure tab and a Text messages (SMS) panel appears. Click Search numbers (optionally filtering by US area code), pick a number, and add it for a flat $0.99/mo — the number becomes the worker’s own line. Release it anytime from the same panel and the monthly charge stops.

Two-way texting. Anyone can text the worker and it texts back from the same number. The worker remembers each person’s conversation separately — every phone number is its own ongoing thread — so a follow-up text picks up right where it left off. These text conversations stay private to the texting and never appear in the worker’s in-app Chat tab.

Replies are automatic. Texting a person back is the whole point, so the worker replies on its own — without waiting for your approval, even under the default policy — and keeps replies short and conversational, like a real text. Other risky actions (texting a different number, sending email, and so on) still follow the worker’s approval policy.

STOP and HELP are handled for you. If someone replies STOP (or UNSUBSCRIBE, CANCEL, END, QUIT) or HELP, the standard carrier opt-out / help reply is sent automatically and the worker is never woken — so it can’t text someone who opted out. START opts them back in.

If a text can’t be delivered — for example a landline, or a number that blocked messages — you’ll get a heads-up in your in-app notifications.

Enable Make a phone call in the worker’s Configure tab and a Phone calls panel appears. Search numbers (optionally by US area code), pick one, and claim it — the number becomes the worker’s own line for live calls. Release it anytime from the same panel and the monthly charge stops.

Natural, two-way calls. The worker talks in real time — it listens, responds, and can be interrupted just like a person. Turn Answer incoming calls on so people who dial the number reach the worker, and Allow outbound calls on so it can place calls itself toward a goal.

Tune the experience. Pick a voice, write an opening greeting, set how long a call may run, and add a number to warm-transfer to when a caller needs a human.

Recording is optional. Turn Record calls on to save call audio for later review — it’s off by default. When it’s on, add a recording-consent line and the worker reads it at the very start of the call. Check the consent laws where you operate first — many places require everyone on the call to agree.

Every call is logged. A Recent calls list in the same panel shows each call with its status, length, and outcome. Open one to read the full transcript, a short written summary the worker puts together after the call, the key points — and, when recording is on, play back the audio right there.

Voicemail is handled. On calls the worker places, if an answering machine or voicemail picks up, it recognizes that, marks the call as voicemail, and hangs up instead of talking to a machine.

Booking appointments. If you’ve enabled Run a connector action and connected a calendar, the worker can book an appointment during the call — it confirms the day, time, and who it’s for out loud, then adds it to your calendar right after you hang up.

After every call the worker automatically carries out any follow-ups it promised — a recap text, an email, a saved note, a calendar event — once the call ends. During the call it never sends those itself; it lines them up for afterward so nothing risky happens mid-conversation without your policy applying.

A worker can diagnose itself. Ask it why something isn't working — or just ask it to do something on a channel that's broken — and instead of a dead-end "I can't", it runs a checkup across its channels (Telegram, email, texting, calls), connections, credits, and setup, then tells you the exact cause and the exact fix. For example: "your Telegram account is linked, but this worker isn't connected to your chat yet."

Some fixes it can run itself. A small, fixed set of safe repairs — connecting the worker to your already-linked Telegram chat, setting up its agent inbox, or detaching a dead tool server — can be done by the worker on your say-so. Repairs count as risky actions, so under the default policy the worker always asks before running one. It can only ever fix its own settings: repairs can never change code, spend money, claim phone numbers, or touch anything outside this worker.

Fixes only you can do— like linking your Telegram account for the first time or claiming a text number — come back as step-by-step instructions with a link to the right screen. The same checkup lives in the worker's Configure tab as a Run checkup button, and if a channel that used to work breaks (say you pause your Telegram link), you get a one-time heads-up notification with the fix.

Workers learn from their runs. A failed run leaves the worker a short lesson it remembers next time, and when a worker keeps hitting the same wall, it drafts a set of operating notesfrom its recent failures. Nothing is applied automatically — the draft waits in the worker's Insights tab for your review, you apply or dismiss it with one click, and you can roll an applied note back afterwards.

Every worker opens inside Theo Chat with a Chat tab — a built-in conversation where you give it direction, ask it to do something, or just talk a goal through. Send a message and the worker gets to work in the background, then replies right in the thread.

When it needs your sign-off, an Approve / Reject card appears inline in the chat — approve and the worker picks up exactly where it paused. The in-app chat and a bound Telegram chat share the same ongoing conversation, so you can start a thread on your desktop and keep it going from your phone.

Replies and step-by-step progress appear live as the worker works — you’ll see a short note each time it finishes an action, then its full reply, without refreshing.

Attach files and projects. The + button in the composer lets you upload files (images, PDFs, docs, sheets) or add existing projects from My Projects — pick a presentation, note, flowchart, or whiteboard from a thumbnail gallery and the worker reads its content as context for that turn (up to three projects at a time). Attached projects are read-only reference — the worker won’t edit them.

Naming and pinning. By default a worker quietly renames itself as your conversation shifts, so the picker always reflects what it’s working on. To keep a name, click the name in the worker’s header to rename it, or use the pin toggle beside it — a pinned name is never auto-renamed. You can also manage this with the Auto-name from chat switch in Configure.

Theo Claw lives right inside Theo Chat: open the Theo Claw tab in the chat sidebar to see your workers, pick one to open its chat, and switch between workers anytime from that same list. Its chat, configuration, runs, and insights all open right inside chat — switch back to your Theo Chat conversations any time from the same sidebar without losing them.

Give a worker a team of helpers and a single thread becomes a team chat — when it hands a sub-task to a teammate, that teammate’s reply shows up in the same conversation, labeled with its name.

Bind a worker to a Telegram chat and it becomes a teammate you can message. Send it instructions to kick off a run, get its replies delivered back to the chat, and answer its approval prompts right there with Approve / Reject buttons — no need to open the app.

The chat has memory. The worker remembers your ongoing Telegram conversation across runs and replies conversationally right in the chat, so a follow-up message picks up where you left off. Voice notes are transcribed and uploaded documents are read in as text — talk to it the way you'd talk to a person.

Operator commands let you start a fresh run, reset the worker’s memory of the current conversation so it starts clean, and check what it’s doing — all without leaving Telegram.

Deploy turns a worker on so it responds to its trigger; Pause stops it without losing any configuration or history. Both live in the worker’s Theo Claw tab in Theo Chat.

The Runs tab lists every execution with its per-step status, duration, and any error, so you can see exactly what the worker did and when. The Insights tab rolls those runs up into a health snapshot — success rate, typical duration, and the most common failure reasons — so you can tell at a glance whether a worker is pulling its weight.

• Manual — you run it on demand from the workspace or by messaging it.
• Schedule — it runs on a recurring cadence you set.
• Event — it wakes up when something happens in your workspace.
• Telegram — a message to its bound chat starts a run.

Scheduled and event-driven runs happen in the background with the same step and time budget as a manual run, so a multi-step worker finishes instead of being cut off early.