A bot is a teammate with its own name, job and memory. You talk to it in conversations, and it works in a space of its own where it keeps files, runs commands, and can publish what it builds as a page on harner.app. You can close the tab: the work carries on, and the files stay where it left them.

On your home page at /me. It shows what needs you, what your bots did recently, and this month's usage. A new account sees one thing there: make your first bot. Every bot is listed under Your bots.

Yes. A routine is what to do and when. The bot runs it on that schedule without you, and you read the result in its conversation.

Yes. A conversation's Export menu downloads it as Markdown or as JSON, so the work can continue somewhere else. A transcript holds whatever the conversation contained, so read it before you hand it to somebody else.

No, when the service offers harner-v1, the model that comes with Harner, billed per token. You can also use a key from a provider you already pay, and that provider bills its tokens. The key needs an account with credit on it. You can make one at OpenAI, Anthropic, Google, Groq, OpenRouter or xAI, and store it on the Keys tab.

Yes, the ones you give it. A secret reaches the bot as an environment variable, the same way it would on GitHub Actions or Vercel, and the bot can print it. Storing it here keeps it off your screen and out of the logs. It does not hide it from the bot you asked to use it.

harner-v1 by the token, and compute by the second: the CPU and memory a bot holds while it works, and the disk its files live on. There is no seat fee and no minimum. The pricing page has the numbers, and your billing page shows your month so far.

Stored model keys and secrets are encrypted. The server holds the decryption key, so this protects a stolen database file, not a stolen server. The harner.dev team holds an admin key that can read any account's transcripts.

Conversation history older than 30 days is removed. Finished API tasks are removed after 7 days, except the latest hundred across the service. Those are this service's defaults.

Which bot, 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.