Teams

One server for everyone you build with.

Most agent apps are a remote control for one person. Polyth is a shared workspace: each person signs in as themselves, chats stay private until they are shared, and the owner decides what every account may do.

Real boundaries, enforced by the server.

A Space owns its projects, chats, files, worktrees, knowledge, secrets and integrations. One person can keep several — home, a side project, work — and a team can share one. Every request is checked against membership on the server; the interface never decides who sees what.

  • Owner

    Owns the Space and decides who belongs to it.

  • Admin

    Manages the Space and the chats shared with all of it. Cannot open private chats.

  • Member

    Starts chats, works in shared ones and runs agents.

  • Viewer

    Reads the chats shared with the Space.

Sharing

Private until you share.

  • Private by defaultEvery new chat is private, however many people are in the Space, so inviting someone later never exposes old work.
  • Share on your termsShare a chat with specific people or the whole Space, to read along or to work in it together. Helper agents started from a chat follow its access.
  • Admins don't read over your shoulderManaging a Space gives no access to the private chats in it.
Share “Release checklist”

People and agents, in one place.

  • Who said what

    Every message carries its author, and the agent works with the accounts of the person who sent it.

  • Conversations with people

    Talk to teammates with @-mentions and notifications, then start an agent session from the thread in one step.

  • Your own accounts

    Each person connects their own accounts, such as Google, and chooses the Spaces where they apply.

  • Shared service accounts

    A Space can hold team accounts too. Agents use them only if the Space allows it, and that is off by default.

  • A place to start

    New people get a private personal project, so they can start chatting before anyone explains folders.

  • Devices and tokens

    A paired phone can do nothing until it is granted access. Command-line tokens belong to one person and can be revoked at any time.

Control

The owner stays in charge.

  • Account limitsAllow only selected projects — the rest, with their chats and files, stay invisible — only selected assistants, and a number of messages or new chats per day. Today's use is always visible.
  • Protected modeOnly the features and models the owner granted, no composer shell, no Auto-approve or Full access, no "always" answers. A Space with a protected member never answers on its own.
  • Account managementRename accounts, reset a password and sign the person out everywhere, or pause sign-in without disabling the account.
  • Usage across agentsTokens, cost and time per session, project and the whole server, and live provider limits with a pace warning.

One server. Everyone on it.

Run Polyth on a machine your team can reach, invite people, and let the server keep the boundaries.