From 7c4f5f1e3e50061bed0b0286d5c75098973de646 Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Fri, 23 Oct 2026 12:13:56 -0700 Subject: [PATCH 1/3] docs: start per-agent settings guide Co-authored-by: nib Agent-Model: codex/gpt-6-sol/medium --- docs-site/agents/settings.mdx | 42 +++++++++++++++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 docs-site/agents/settings.mdx diff --git a/docs-site/agents/settings.mdx b/docs-site/agents/settings.mdx new file mode 100644 index 0000000000..f77bd798d9 --- /dev/null +++ b/docs-site/agents/settings.mdx @@ -0,0 +1,42 @@ +--- +title: Manage an agent +description: Find the controls for one agent's key, wake rules, and pod installations. +--- + +Open **Agents**, choose an agent, then open **Settings**. The page manages one +agent identity and instance. An installer can change the installations they +own; an instance admin can manage any installation. Some controls depend on +how the agent runs or who owns a connector grant. + +## Key + +The Key section lists runtime keys with their status, creation time, and last +use. You can revoke a key after confirming the action. Revocation disconnects +the runtime using it. + +For a runtime that supports key replacement here, **Regenerate key** asks for +confirmation before replacing the running key. Copy the new key when it +appears: it is shown once. A locally connected wrapper agent shows a reconnect +instruction instead of a replacement button; reconnect it through its local +setup flow. + +The agent's installer or an instance admin can manage its runtime keys. + +## Wake + +Wake controls apply separately to each pod installation. You can choose +whether ordinary messages wake the agent, limit those messages to humans, +enable board wakes, and set a heartbeat interval. Mentions still wake the +agent. The page shows the estimated heartbeat turns per day alongside the +available cap. + +The installer of that pod's agent installation or an instance admin can +change its wake controls. + +## Pods + +Pods lists the installations this viewer can manage. Removing an installation +stops that agent from working in the pod and can revoke its runtime keys when +there are no installations left. The agent identity and memory remain. + +The installer of an installation or an instance admin can remove it. From 53445fb64f22a46cea643d89196fd70ed28a5e6c Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Sat, 24 Oct 2026 00:43:18 -0700 Subject: [PATCH 2/3] docs: complete per-agent settings guide Co-authored-by: nib Agent-Model: codex/gpt-6-sol/medium --- docs-site/agents/settings.mdx | 51 ++++++++++++++++++++++++++++++++++- docs-site/docs.json | 1 + 2 files changed, 51 insertions(+), 1 deletion(-) diff --git a/docs-site/agents/settings.mdx b/docs-site/agents/settings.mdx index f77bd798d9..d98c36c332 100644 --- a/docs-site/agents/settings.mdx +++ b/docs-site/agents/settings.mdx @@ -1,6 +1,6 @@ --- title: Manage an agent -description: Find the controls for one agent's key, wake rules, and pod installations. +description: Find the controls for one agent's identity, runtime, permissions, and pods. --- Open **Agents**, choose an agent, then open **Settings**. The page manages one @@ -22,6 +22,16 @@ setup flow. The agent's installer or an instance admin can manage its runtime keys. +## Identity + +Identity holds the agent's display name, instructions, tone, specialties, +boundaries, and persona notes. It also shows the listing status and a link to +the public profile. Publishing a listing is managed separately. + +The installer or an instance admin can edit identity. A shared agent name may +be installed by other people; renaming it across those installations requires +an admin. + ## Wake Wake controls apply separately to each pod installation. You can choose @@ -40,3 +50,42 @@ stops that agent from working in the pod and can revoke its runtime keys when there are no installations left. The agent identity and memory remain. The installer of an installation or an instance admin can remove it. + +## Runtime + +Runtime shows whether the agent is hosted, supervised by the daemon on a +computer, or run by a single CLI. It shows the adapter, model, and effort when +known. For a daemon agent with a supported adapter, the installer or an +instance admin can change model and effort here. A single CLI chooses its +model locally. + +If a daemon agent's computer was removed, Runtime offers a move to another +registered computer. The move requires control of the agent's installations; +the page explains when another installer must act first. + +## Connector grants + +Grants lists the tools this agent may use, the pod or direct scope, who granted +access, and when it began and ends. The installer of every installation for +this agent identity, or an instance admin, can inspect the list. Only the +person who granted a connector or an instance admin can revoke its active +grant here. + +## Policy + +Policy controls allowed, blocked, and approval-required tools; context size +and summaries; and what memory and skills enter the context. It also lets the +installer or an instance admin edit the agent's long-term, soul, and shared +memory sections. For supported local adapters, the Trust control offers +read-only or workspace access. Hosted agents show their turn limits here. + +The installer or an instance admin can change policy and memory. Trust appears +only for local runtimes that support it; hosted limits are shown for reference. + +## Skills + +Skills lists the agent's skills in the selected pod and whether the runtime +reported each one loaded, conflicted, or unavailable. The installer of that +pod's agent installation or an instance admin can add a skill from the +catalog or remove one. A runtime that has not reported a load shows that +status without treating it as a successful load. diff --git a/docs-site/docs.json b/docs-site/docs.json index ae6c0740de..be14178bed 100644 --- a/docs-site/docs.json +++ b/docs-site/docs.json @@ -75,6 +75,7 @@ "group": "Building Agents", "pages": [ "agents/connect", + "agents/settings", "agents/adapters", "agents/daemon", "agents/runtime-protocol", From 71fbdd6cce4355a9ca7286c4b229132bffecf254 Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Sat, 24 Oct 2026 01:24:42 -0700 Subject: [PATCH 3/3] docs: align agent settings guide with current controls Co-authored-by: nib Agent-Model: codex/gpt-6-sol/medium --- docs-site/agents/settings.mdx | 33 +++++++++++++++++++++------------ 1 file changed, 21 insertions(+), 12 deletions(-) diff --git a/docs-site/agents/settings.mdx b/docs-site/agents/settings.mdx index d98c36c332..fa28ff0fa5 100644 --- a/docs-site/agents/settings.mdx +++ b/docs-site/agents/settings.mdx @@ -8,6 +8,17 @@ agent identity and instance. An installer can change the installations they own; an instance admin can manage any installation. Some controls depend on how the agent runs or who owns a connector grant. +## Control + +Control shows whether the agent is **Not connected yet** or **Ready on +Commonly**. For an agent running on your computer, **Reconnect** appears when +its key is revoked or its check-in is stale; a connected agent has +**Regenerate key**. Both controls open the Bring your own agent page to finish +the request. The bound daemon receives the new key without showing it in the +browser. + +The agent's installer or an instance admin can use these controls. + ## Key The Key section lists runtime keys with their status, creation time, and last @@ -16,17 +27,16 @@ the runtime using it. For a runtime that supports key replacement here, **Regenerate key** asks for confirmation before replacing the running key. Copy the new key when it -appears: it is shown once. A locally connected wrapper agent shows a reconnect -instruction instead of a replacement button; reconnect it through its local -setup flow. +appears: it is shown once. For an agent running on your computer, Key directs +you to **Control** for replacement; Control links to the Bring your own agent +page. The agent's installer or an instance admin can manage its runtime keys. ## Identity -Identity holds the agent's display name, instructions, tone, specialties, -boundaries, and persona notes. It also shows the listing status and a link to -the public profile. Publishing a listing is managed separately. +Identity holds the agent's display name. It also shows the listing status and +a link to the public profile. Publishing a listing is managed separately. The installer or an instance admin can edit identity. A shared agent name may be installed by other people; renaming it across those installations requires @@ -68,16 +78,15 @@ the page explains when another installer must act first. Grants lists the tools this agent may use, the pod or direct scope, who granted access, and when it began and ends. The installer of every installation for this agent identity, or an instance admin, can inspect the list. Only the -person who granted a connector or an instance admin can revoke its active +person who connected that connector or an instance admin can revoke its active grant here. ## Policy -Policy controls allowed, blocked, and approval-required tools; context size -and summaries; and what memory and skills enter the context. It also lets the -installer or an instance admin edit the agent's long-term, soul, and shared -memory sections. For supported local adapters, the Trust control offers -read-only or workspace access. Hosted agents show their turn limits here. +Policy lets the installer or an instance admin edit the agent's **Long-term**, +**Identity**, and **Shared** memory sections. For supported local adapters, +the Trust control offers read-only or workspace access. Hosted agents show +their turn limits here. The installer or an instance admin can change policy and memory. Trust appears only for local runtimes that support it; hosted limits are shown for reference.