A session is a shared Nuphos conversation backed by your connected agent.
You describe what you want in plain language and the agent investigates and acts
against your connected infrastructure, streaming its progress as it goes. The
workspace is tab-based, so you can run several sessions side by side.
Starting a session
First make sure the workspace agent runtime is online. Then
open Agent and start a new session. Each session keeps its own
conversation history, so use separate sessions for separate threads of work — one
for an incident, another for a routine check.
Selecting credentials
Before the agent can touch a cloud account, you select which credentials the
session may use — for example a specific AWS account or GCP project. This is the
core of least-privilege in Nuphos:
- The agent only ever sees the credentials you select for that session.
- You can only select accounts you’re allowed to use (the account’s
member allow-list).
- Credentials are short-lived and minted on demand — see
the IAM trust model.
Give a session only the accounts it needs. If you’re investigating staging,
don’t hand it production.
Mentioning resources
You can reference Nuphos resources directly in your prompt with mentions,
instead of describing them in prose. Mention a cluster, a deployment, or an
account and the agent resolves it precisely — no ambiguity about which “api”
service you meant.
How the runtime works
Nuphos sends the prompt, selected credentials, team context, memory, and skills
to the workspace runtime. As your agent thinks and executes, Nuphos streams its
tool calls and results into the shared transcript. It has a shell, cloud and
Kubernetes APIs, web lookups, Nuphos APIs, and reusable skills.
The runtime is durable: a conversation reattaches to the same inner agent
session after an app, backend, or runtime restart. If you send another message
while a turn is active, Nuphos queues it and steers the running conversation at
the next safe boundary.
When the agent wants to change something, it doesn’t just do it — it proposes
a plan for you to approve.
History & long sessions
Conversations are persisted, so you can leave and come back. Long sessions are
compacted automatically — older turns are summarized while recent context is
kept verbatim — so a session can run for a long time without losing the plot.
Beyond the desktop
Your connected agent isn’t limited to the desktop app. You can talk to it from
Slack or iMessage, and run it automatically with
triggers. Nuphos can expose the same workspace to other
terminal coding agents supported by
OpenAB as those runtimes become available. 
