A bot is a machine with its own character, memory, disk, and shell. You talk to it, and it edits files and runs commands in there. Nothing it does leaves that machine. You can hire it and close the tab. The work stays.

Harner includes the built-in harner-v1 choice when the service operator enables it. Otherwise, you bring a key from a provider and they bill the tokens. You need an account with credit on it. You can make your own keys at OpenAI, Anthropic, Google, Groq, OpenRouter or xAI. Store one on your keys page. After that a request only needs a model name.

Sign-in with GitHub lands on your home page at /me — what your account has run, all time and this month. Your bots are at /me/sandboxes.

Stored model keys are encrypted. The server holds the decryption key, so this protects a stolen database file, not a stolen server.

A finished session is kept for 30 days and a finished task for 7, then swept. The harner.dev team holds an admin key that can read any account's transcripts.

The seconds a bot is awake. That is the CPU and memory it holds, from the moment the machine is ready until you put it to sleep or delete it. The pricing page has the numbers. Your own figures are on your billing page.

No. Nothing here stops or deletes a bot except you. If you leave one awake, it keeps costing until you put it to sleep. Your bots lists what is up.

A persistent bot keeps its disk. Sleep it and wake it, and the files are where you left them. A temporary one has no disk of its own. Its files go with the machine. You chose which kind when you hired it. Your bots page says which.

Yes. They arrive as ordinary environment variables, the same way they do on GitHub Actions or Vercel, and the bot can print them. Storing them here keeps them off your screen and out of the logs. It does not keep them from the bot you asked to use them.

Yes. A routine is a prompt and a cron expression. It keeps its own machine between runs so it can leave itself notes. Put an address on it and you get an email when it finishes, including when it fails.

Yes. Every session is kept. You can reveal and download it from your bots as Markdown, structured JSON, or the raw log, so the work can continue in another agent. A transcript has whatever the session contained. Read it before you hand it to a third party.

The bot id or the task id, roughly when it happened, and what you expected instead. Every reply this service sends carries a request_id. If you have one, send that first.