Pimpo
Documentation

User guide

More

Everything else in the guide.

Settings history#

Settings › History lists every change to rules and the safety level, the budget, connections, models, people and the other settings, newest first, with who made it and when; filter it by area. Undo (after a confirmation) puts the earlier values back. Undo starts from the newest change: a setting changed again since must have that newer change undone first. Passwords, keys and tokens are never kept in the history, not even encrypted: it only says one was added, replaced or removed, and to change one back you type it again. Adding or removing a person is not undone here. A member finds the history of their own mail and calendar in Account; nobody else sees it, the administrator included.

Dashboards in Telegram#

When Pimpo has a public https address (From anywhere with Tailscale Funnel, or your own https address under Use another address, in Settings › Open on your phone), the bot adds a Dashboard button next to the message box of everyone who paired Telegram, and notices that wait for an answer get an Open dashboard button. It opens a small Pimpo inside Telegram, on the phone, the desktop app or Telegram Web:

It signs you in as the person who paired that Telegram account, with nothing to type, and shows only your things; guests see what guests may use. The session lasts an hour; after that, close it and open it again from the bot. Telegram opens only https pages, so without a public https address the button does not appear (and goes away if the address does). A Telegram account nobody paired gets nothing.

Keys Pimpo asks for#

When a routine or a task needs a password or key you have not given (a GitHub token, a Notion integration token, your email's app password), or the service stops accepting the one you gave, Pimpo asks for it privately. You get a notice, "GitHub needs your token", with a link to a form in the app; the request also waits in Needs you. The form writes the key straight to Pimpo's vault, under your name: a member's keys are theirs and the administrator never sees or answers their requests. After saving, Run the routine again or Try the task again picks up where it stopped. The link works once and expires after a week.

Never send a key in a chat or a channel message. If you do, Pimpo takes it out before the message goes anywhere (the model, the conversation, the activity log) and does not keep it; it tells you so and points you to the form. It recognizes common formats (API keys of the big providers, GitHub, Slack and Telegram tokens, private keys) and values written after "password:" or "token=". It removes only what looks like a key, so the rest of your message still goes through.

Secrets in 1Password or HashiCorp Vault#

Any secret field (a model key, a bot token, a connector's key, an app password, the backup passphrase) can hold a reference instead of the secret: choose the link icon, Use a reference, and type where the secret is:

Check reads it once and says only "Found" or why not; the value is never shown. Pimpo keeps only the reference and reads the value when a connection needs it, keeping it in memory for up to five minutes. If the reference cannot be read later, the connection fails with a message that names the reference.

Set up the password managers first. The administrator sets up the house's in Connections › Password managers; they read the house's references. Each person can add their own in Account › Password managers, and only their own connections use them: nobody else sees them or reads with them, not even the administrator, and a person's references never read with the house's credentials.

Test checks that the password manager answers. Backups and exports keep the references as references, so a restored copy reads from the same place.

This page is built from the repository's documentation. Improve it on GitHub.