Skip to content

Security

pi-roundtable runs one assistant for one owner. Discord and the web chat both work, and you can let other people talk to the assistant. It does not yet isolate those people from each other the way a multi-user service must; whoever lets them in takes that on.

  • The operator controls the host, its configuration, and its credentials.
  • An owner, one listed in access.owners, may use every tool.
  • Everyone else is admitted at a tier, member or admin, by the access rules over verified identities and roles, such as a Discord user id or a role of the web chat’s token. See Access tiers.
  • No token claim makes anyone the owner.
  • A turn gets only the tools its speaker’s tier holds, and a tool no plugin gives a tier is the owner’s alone.
  • Tools run in the host process, with its files and its network. web_search and fetch_content can reach internal addresses, so name the tools of a web persona in its selection.
  • Plugins run in the same process, with the same access.

A held call is approved only by the speaker whose turn held it, at a tier that still holds the call, or, in a shared conversation, by an owner. That holds for the approval card and for a confirming message. A call that someone above the speaker should approve needs a higher minTier, or a hold rule’s approvalTier.

  • In Discord an agent’s channel and a group room are shared: everyone who writes there adds to one conversation the agent reads.
  • A web chat conversation belongs to the person who opened it: in the web chat only they may read it, write in it, or answer its prompts, but the owner can read it through the owner console, and the operator through the database and the data directory.
  • Each speaker’s memory is their own. One person who writes from Discord and from the web has two identities and two memories.
  • Model credentials. Every turn, whoever speaks, runs on the host’s model login and is billed to it.
  • Identity. One person on two networks is two speakers.
  • Data. Conversations, memory, and schedules sit unencrypted in PostgreSQL and the data directory.

Later releases add one identity per person across networks, and per-person model credentials.