##\ ##\
## | ## |
#######\ ##\ ##\ ######\####\ #######\ ######\ ######\
## __##\ ## | ## |## _## _##\ ## __##\ ## __##\\_## _|
## | ## |## | ## |## / ## / ## |## | ## |## / ## | ## |
## | ## |## | ## |## | ## | ## |## | ## |## | ## | ## |##\
## | ## |\####### |## | ## | ## |####### |\###### | \#### |
\__| \__| \____## |\__| \__| \__|\_______/ \______/ \____/
##\ ## |
\###### |
\______/
A private AI assistant. There is no account to make — a key on this device is the whole of it.
The same key you use in Nymchat, or any other Nostr app. It stays on this device.
By continuing you agree to the Terms and Privacy Policy.
Nobody can reissue either of these — not even us. Without them, this identity, its history and any credits on it are gone.
The second one seeds the key that makes your messages quantum-resistant. Paste it into another device to link it to this account.
Email us and say what you were doing when it went wrong. We cannot read your chats — they are encrypted to keys we do not hold — so the more you can tell us, the more we can help.
A prompt Nymbot sends for you on a schedule. There is no server doing this: it runs while the app is open, and a run that came due while it was shut runs once when you come back rather than catching up on all of them. Each run costs a reply, like any other.
A bot is a way of answering: a name, standing instructions, a model and a few openers. Share one as a link or publish it under your npub. A shared bot carries none of your repositories, tokens or files — only how it answers.
Paste a bot link or an address published on Nostr.
A workspace is standing context: instructions, reference files and repositories that every chat in it starts with. The files stay on this device and travel only inside the first message of a chat that uses them.
The same prompt goes to two models on separate threads, so neither sees the other's answer. Keep the one you prefer and the chat carries on from it. Two replies means two charges.
Connect as many repositories as you like and tick the ones this chat can see. Pro replies read their code and, with writes on, commit, branch and open pull requests. Access tokens are stored only on this device and sent to the Nymbot worker per request — never stored server-side or published to relays.
A persona is a standing instruction sent with the first message of a chat. It never leaves your device except as part of that message.
Sent once, with the first message of this chat, on top of any persona.
A reply that produces a whole file — a page, a script, a document — opens it here beside the chat, where you can read it, edit it and keep the versions.
Standing facts Nymbot carries between chats, kept one at a time so each can be read, corrected or thrown away on its own. They live on this device; the few that bear on a question travel inside that message, encrypted like everything else you send. A ghost chat neither reads them nor adds to them.
Comma separated. Tags show in the chat list and are searchable.
A repo task can stop mid-way when it has used its allowance of model calls. Carrying on buys it another allowance from the same balance, one leg at a time, and every leg says what it cost. Stop cancels the rest.
Swept when the app opens. Pinned chats are never swept.
Your chat is already end-to-end encrypted, but Nymbot still sees which pubkey is talking to it. Turn this on and every message, and every reply, travels under a throwaway key generated on this device. Credits move across as blind vouchers Nymbot signs without seeing, so its own records cannot link the two.
When the throwaway key runs low, move credits across without asking. Same blind vouchers, same unlinkability — it just saves doing it by hand before every chat.
Spends that many credits from your nym and mints the same value onto the throwaway key. Nymbot signs the vouchers blind, so it cannot match what it spent to what it later accepts.
Both are the same key in two spellings, and both are safe to share — they are how somebody addresses you.