Skip to main content
Nuphos is an agent workspace for teams. These concepts describe who participates, where the work runs and which context and access it can use.

​
Teams and sessions

A team groups connected tools, members and shared settings. A member’s role is Administrator, Editor or Viewer. Administrators manage membership and team connectors; Editors can work with agents and permitted connections; Viewers have read-only access. See Teams & members. An agent session is the conversation you give a job to, with its transcript and task context. The app also calls it an agent. Start separate sessions for separate jobs. Sharing a session lets teammates read or contribute according to its access settings; team membership alone does not grant access to every private conversation or to the computer running it.

​
Computers and runtimes

  • A computer is a machine: your laptop, your server, or a managed cloud computer.
  • A runtime is a supported coding tool installed there, such as Claude Code or Codex. It keeps its provider’s harness and sign-in.
  • A session runs on a runtime. Moving it changes where future work executes; it does not copy every repository, secret or local file to that machine.
Supported runtimes have different sign-in, model and platform support. Local work needs your machine running. Remote work can continue after you disconnect. Managed capacity has a computer plan; model-provider billing is separate.

​
Workspace and context

Desktop can show several sessions in split panes and tools in the dock beside them: browser tabs, terminals, desktops and artifacts. Connected resource pages let you inspect accounts and resources and start an agent with that context. They are convenient views, not the limit of what a provider’s authorized CLI or API can do. See Desktop app.

​
Shared and personal knowledge

Instructions give recurring guidance. Skills package procedures and supporting files. Memory stores durable facts and verified playbooks for later retrieval. Team and personal scopes are separate; sharing a team does not share every personal setting or credential. Agents must save and retrieve memory explicitly rather than receiving the whole memory store automatically. See Skills and Memory.

​
Credentials and permissions

Connect the tools a task needs and select the allowed connections for the conversation. Team roles, connector allow-lists, conversation selection and the provider identity’s own permissions all matter. Personal GitHub, Linear, Gmail and Drive connections belong to the member who connected them. Federated cloud connections mint short-lived credentials. Other integrations store an encrypted token or client secret, or proxy access server-side. The mechanism depends on the connector. A local runtime can also use sign-ins already on its computer; that is a separate reason to share machines carefully. See Access control and IAM trust model.

​
Plans and action approvals

A plan makes significant cloud infrastructure work reviewable: scope, decisions, execution steps, risk and cost. It is not a universal gate on every write. Auto Mode and Full Access separately control the runtime’s action permission prompts. Neither can grant a cloud permission missing from the connected identity. See Plans and permission modes.

​
Automation

A trigger starts work from a schedule or webhook. A Watch wires a provider alert to an agent workflow. These require persisted setup; leaving a command running in a session does not create a durable monitor. Review the runtime, credentials, permission mode and destination before automating a task. See Triggers & automation.