terminal · waiting for container

Provision an agent to open the web terminal.

The terminal is a signed iframe straight into your tenant container on agents-01. It appears here as soon as the container is up — usually about 5 minutes after the first key + Telegram bot are wired.

Get started → See pricing

Signed link, 10-minute TTL, auto-refreshed every 8 minutes. Nothing to set up — once your tenant is provisioned, it just works.

terminal · docker exec to your agent

Your shell, your container.

Real web terminal straight into your agent's Docker container. Signed link, 10-minute TTL, auto-refreshed every 8 minutes.

checking…

⬛

Connect your agent first.

Add a model key in Get started — once the container is provisioned, this becomes your live shell.

→ /dashboard/setup See pricing

Example session — what this looks like once your agent boots

you@your-agent ~ /srv/agent tty 24×80 · UTF-8

you@your-agent ~ $ ls
crons.yml   keys.yml   memory/   plugins/   logs/   docker-compose.yml

you@your-agent ~ $ cat crons.yml | head -10
# Crons your agent set. You can also edit by hand — it'll reload.
- name: inbox-digest
  schedule: "0 9 * * *"
  task: skill.inbox_digest --tz Europe/Amsterdam
- name: weekly-review-draft
  schedule: "0 17 * * 5"      # added by agent · you asked
  task: skill.draft_review --src notion --dest telegram

you@your-agent ~ $ agent install slack-mcp
[+] Pulling slack-mcp@0.4.2 from registry ... ok
[+] Adding to plugins/, restarting agent ...
[+] slack-mcp ready. Try: "watch #design channel for keyword 'release'".

you@your-agent ~ $ ▋