Send a message, a photo, or a voice note. The bot's AI reads it, decides what needs doing, and actually does it — inside a Linux directory and shell that belong only to you. No app to install, no server to rent.
This is the actual order of events, every time you send something — not marketing steps, the real pipeline.
Plain text, a photo, or a voice note. Nothing needs a special format — talk to it like you'd talk to a person.
A language model (hosted on Ollama) looks at your message plus the recent conversation, and works out whether it can just answer, or whether it needs to do something first.
Run a shell command, read or write a file, list a folder, look at an image, or open a public link for a web app you started — the model picks exactly one tool and the arguments for it.
Inside your own sandbox directory and persistent shell — python3, pip, node, and npm are already installed. Real output, real errors, nothing simulated.
Command output, file contents, an image description, a transcript — whatever came back is fed to the AI so it can judge what to do next.
The loop continues — fix, re-run, check again — until the model has something worth telling you. You watch it happen live, in one message that updates as it works.
Each of these is a tool the AI can reach for on its own, or you can drive directly with a command.
A persistent bash shell that remembers your working directory between messages. Ask it to run something, read the error, and fix it — it will, on its own.
Send anything — a script, a dataset, a zip. Archives (.zip, .tar, .tar.gz) are extracted automatically.
Start a web app or API and get back a real, clickable public URL through a Cloudflare Tunnel — no deployment step required.
Send a photo — a screenshot, an error, a diagram — and ask what's in it, or let the AI look at its own output to sanity-check itself.
Voice notes are transcribed and handled exactly like a typed message — same tools, same sandbox, same conversation.
Check your storage, list or download files, and wipe everything clean whenever you want a fresh start.
Every command below works at any time, even mid-conversation with the AI — nothing blocks anything else.
| Command | What it does |
|---|---|
/start | Introduction and quick orientation. |
/help | Full command list, right in the chat. |
/shell <cmd> | Run one command in your persistent sandbox shell. |
/run <code> | Quick one-off Python, e.g. /run print(1+1). |
/stop | Interrupt whatever's currently running. |
/files [path] | List files in your sandbox. |
/storage | Show how much of your quota you've used. |
/download <path> | Get a file back out of your sandbox. |
/expose <port> | Get a public URL for a local app you're running. |
/tunnels | List your currently active public links. |
/reset | Wipe your sandbox completely and start clean. Irreversible. |
/newchat | Clear the AI's memory of your conversation — your files stay put. |
/pwd | Show your current sandbox path. |
Written plainly, not as a legal document. If something here would change your mind about what you upload, that's the point of reading it first.
Text and images are sent to an Ollama-hosted model to generate a response; voice notes are sent to Groq's transcription service to turn them into text. Both are outside processing, the same way any AI chatbot works — don't send anything you wouldn't want handled by a third-party service.
Each user gets their own directory and shell, kept apart with OS-level limits — timeouts, memory caps, path checks. That stops accidents and casual overreach between users. It is not a hardware or VM-grade security boundary, and it doesn't hide your data from whoever runs the bot's server.
Sandbox files, command output, and logs live on the server this bot runs on. Treat it like any shared server you don't personally control — fine for code, experiments, and public data; not the place for passwords, personal documents, or anything sensitive.
The AI remembers recent messages so it can hold a conversation, capped to a fixed number of turns and cleared on a bot restart. Send /newchat any time to clear it yourself — your files aren't affected.
/reset wipes your entire sandbox — files, running processes, public links — immediately and irreversibly. There's no undo, so use it deliberately.
Every account gets a fixed amount of space. Check /storage any time to see what you're using, and clean up with /reset if you hit the ceiling.