Self-hosted autonomous agent stack with Telegram, email, browser tools and temporary human handoffs.
393
Self-hosted autonomous agent stack with scheduled work, Telegram, email, a persistent browser and human assistance. Currently runs Claude Code through Claudebox.
Claude does the work. Claudebox wakes it on a schedule and receives your Telegram messages. Mailbox and the browser expose MCP tools. A small Go service manages human-help requests and the persistent tailnet viewer.
Requires Docker with Compose v2, Make and Git. Use a machine you control and dedicated agent accounts.
git clone https://github.com/psyb0t/autonomous-stack.git
cd autonomous-stack
make init
Edit .env and configure:
TS_HOSTNAME for browser access.Start a conversation with the bot before deploying. Do not run another Telegram poller with the same bot token.
make pull
make up
make status
make up builds the local helper image, validates settings, generates private configuration and starts the stack. The other service images come from Docker Hub. No host Go installation is needed.
make init generates distinct internal API tokens and never replaces an existing .env. Real credentials, runtime settings and data stay ignored by Git.
| Service | Project | Responsibility |
|---|---|---|
claude | Claudebox | Claude Code, heartbeat cron and owner-only Telegram |
browser | Stealthy Auto-Browse | Browser MCP, screenshots, persistent profile and viewer |
mailbox | Mailbox | Email MCP, IMAP reading and SMTP sending |
handoff | Autonomous Stack | Help requests, Telegram notifications and the persistent viewer proxy |
tailscale | Tailscale | Private browser access under a persistent tailnet node name |
The helper uses servicepack for its lifecycle. Optional phone access uses Dikciz Launcher. Claudebox owns scheduling and Telegram polling. No Docker socket, USB modem or extra Telegram client is included.
No ports are published on the host. Tool APIs use bearer authentication on the Compose network. Tailscale Serve exposes the browser viewer at http://autonomous-stack by default. Tailnet membership and ACLs control access; there is no viewer password or expiring link. Anyone permitted to reach that node can control the browser, so restrict its ACLs accordingly. The MCP and browser automation APIs are not exposed through Serve. Nothing uses Funnel or a public tunnel.
The agent can try an encountered CAPTCHA once using a screenshot, or use an optional owner-configured solver. Solvers default off; see CAPTCHA settings. If the selected approach fails, it requests help and pauses that page.
ready when available.http://autonomous-stack and complete the task.done so the agent can inspect the page and resume.The viewer stays available before, during and after help requests. No request ID needs copying, and done never closes browser access. Readiness depends on the agent following the owner's reply, not independent verification by the helper. See handoff behavior.
| Directory | Contents |
|---|---|
data/browser/ | Browser profile and cookies |
data/recordings/ | Browser recordings |
data/workspace/agent/ | Tasks, artifacts and generated MCP settings |
data/claude/ | Default Claude auth directory |
data/claudebox/ | Cron history and Telegram state |
data/mailbox/ | Mailbox operation state |
data/handoff/ | Current help request |
data/tailscale/ | Persistent tailnet identity and Serve settings |
Tracked .gitkeep files keep these directories present. Their runtime contents are ignored. Back up .env, data/ and any external auth directory privately. Cookies and login state are credentials.
.env.example lists operator settings. Configuration covers auth, prompts, mail and optional Dikciz phone MCP access.
After changing .env or pulling source, run make restart. It rebuilds the helper, regenerates configuration and recreates services. make pull refreshes upstream service images. make stop stops services; make down removes containers and the network without deleting persistent bind data.
Claude Code runs with unattended tool permissions. Its accounts, mounts and network define its reach. Use dedicated accounts and a narrow task scope. Prompt instructions do not make hostile pages or email safe.
See deployment for ownership, backup and privilege details.
make format
make lint
make test-coverage
make sec
make generate
Tooling runs in the development image. Normal tests use the race detector and local fixtures, without live Telegram polling, paid Claude calls or public tunnels.
Development and CI describes the release pipeline. A release tag waits for the matching main commit to pass, then promotes its image without rebuilding it.
MIT. See LICENSE, third-party notices and CHANGELOG.md.
Content type
Image
Digest
sha256:5ba07bdf8…
Size
8.7 MB
Last updated
14 days ago
docker pull psyb0t/autonomous-stack