metor runs delegable bots on a machine you own. Each bot has a name, a memory, its own browser and terminal, and a schedule of its own, driven by the official Claude Code or Codex with your login. Open source, one-line install.
curl -fsSL https://www.metor.com/install.sh | sudo bashA fresh Linux server, five minutes, no domain required.
You open a window, get an answer, close it, and everything is gone. Not here.
You create a bot with a name and a role in one or two sentences: what it is for and how it should work. The role becomes its standing instructions. Tasks come later, in the chat, one at a time or as a schedule.
A bot's files, history and session context live in its own directory. Restart the machine and the bot comes back with the context it had. Pause it for a week and it picks up where it stopped.
Every bot gets its own screen with a browser and a terminal, and its own browser profile: sign in to a site once for that bot, and the login stays. Watch the screen at any time and take over with mouse and keyboard when a page asks for a login, a second factor or a captcha.
Put metor on a server and the bots keep working when your laptop is closed and you are asleep. Routines fire on schedule, long tasks run to the end, and what a bot found is waiting in the chat in the morning.
metor runs as one Linux container on a machine you own: a server, an old PC, your Mac. Inside it, every bot has a directory, a session of its runtime, and its own desktop: a virtual screen with a browser window and a terminal. A gateway serves the interface to your phone and to your desktop browser.
Answers stream in as Markdown. Grey tool lines show what the bot is doing, expandable to the full command and its result. When the runtime asks for permission, an approval card appears: allow or deny. A stop button interrupts a running turn; the bot keeps its context.
Next to the chat: the bot's screen, a real terminal in the bot's directory, and a file browser with downloads. Drop files into the chat or paste screenshots; the bot returns files as cards with a preview or a download.
The same interface follows the messenger pattern on a phone: the bot list, then the chat with a back gesture. Side by side is for desktops. No app to install.
Every bot is a session of the official coding-agent harness, Claude Code or Codex, signed in with your own subscription through the official login flow. No API keys, no tokens copied out of a config file, no proxy in between. The same harness you use at your desk, now running on its own.
your Claude subscription
your ChatGPT subscription
GitHub Copilot, ChatGPT
Shared by all Claude bots. When it is used up, Claude bots wait for the window to reset; Codex bots keep going.
Claude Code with Opus, Sonnet or Haiku; Codex with the current GPT models. Mix them freely across bots.
The “New bot” dialog runs the official login of the runtime: a link, a code, done. Once per machine, not per bot.
The sidebar shows the Claude quota for the five-hour and the weekly window; all Claude bots share it.
A registry defines what a runtime is. Claude Code and Codex are the two today; OpenCode is next on the roadmap.
“Every weekday at 7:00, check the front page again and write a fresh digest.” The bot creates the schedule itself and confirms it. A panel lists every routine with its next run; changing, pausing or deleting one is a sentence in the chat.
A run that was missed while the machine was down runs once after the restart, not twenty times.
A routine that has run twenty times without you saying anything pauses itself and tells you so. A schedule nobody looks at should not spend your quota.
Each run is a grey “Routine” message followed by the bot's work, so the history stays one conversation.
$ curl -fsSL https://www.metor.com/install.sh | sudo bashmetor – server installationWhere should metor be reachable?Address [188-68-58-3.sslip.io]: ⏎Pulling ghcr.io/metor-com/metor-box:latest … doneStarting box + Caddy (TLS via Let's Encrypt) … doneYour setup link (24 h, single use):https://188-68-58-3.sslip.io/bots/auth/claim?token=…open it on your phone
The installer installs Docker if it is missing, pulls the image, starts metor behind Caddy with TLS, and prints your setup link as text and as a QR code. You do not need a domain: the installer proposes a name that resolves to your server's address, and a real domain can replace it any time. Already running a reverse proxy? Forward one path and keep your setup.
The first browser gets in with the setup link. Every further phone or computer is linked from a device that is already in, by QR code or pairing code. A device list shows who is signed in, and any device can be removed.
Pull and restart with compose. Bots, histories and routines survive; sessions resume with their context. Backups are three volumes.
Today with Colima or Docker Desktop and a local build; a Homebrew install that sets up everything is on the roadmap.
Inside its container a bot may read, write, run and browse without asking. Approvals are reserved for the boundary: your own machine, and actions with an effect outside, such as sending, paying, publishing.
Harnesses run as processes with their own login. metor never extracts tokens or impersonates a subscription.
No silent uploads, no source maps in releases. Your data lives in three volumes on your machine; a backup is a copy.
Apache-2.0. The image bundles Claude Code and Codex from their official channels; using them needs your account and their terms.
Version 0.1.0 works end to end, with rough edges. The changelog, the backlog and the image are public on GitHub.
A memory engine for company knowledge. It answers your agents with verified facts and exact counts instead of plausible guesses, and plugs into any MCP-capable harness. A product of its own.
Five minutes on a fresh server. Your subscription, your machine, your bots.
curl -fsSL https://www.metor.com/install.sh | sudo bash