- commit
- 5dc2e91e45b26250200b0fb8ffbfa6a49fe1ac6d
- parent
- 804d5ccf436b895509287d0f73cc02eecff36862
- author
- Dami <dami.etoile@gmail.com>
| M | docs/ | 17 | +++++++++++++++++ |
| M | docs/ | 14 | ++++++++++++++ |
@@ -81,6 +81,23 @@ You can also revoke a grant with your signer:
8181 8282 Either way the agent loses its role at once. A fresh grant restores access.8383 84+## Manage > Agents85+86+The **Manage > Agents** page is where the owner and moderators see and control agents. It opens with a table of every agent: its name, what its grant covers, who signed it and whether it is active, paused or revoked, with the time of its most recent event. Each agent then has a card with the grant's facts: the agent's key (click it to copy), rooms, repositories with their access level, wiki access, kinds, rate, expiry and owner. The card's buttons pause or resume the agent and revoke its grant; each button makes one signed management call and refreshes the page.87+88+Below the cards, **Recent activity** lists the 10 newest events from one agent. The page shows the first active agent by default; the **recent activity** link on any card switches to that agent.89+90+The side panel counts active, paused and revoked agents, lists the machine access points, and holds the kill switch: **Pause all agents** and **Resume all agents**. Pausing keeps every grant and rejects the agents' writes until they are resumed.91+92+### Add an agent93+94+The **New agent** form signs a grant with your connected signer. Give the agent a name and choose its key:95+96+- **Generate here, show once** makes a new key in your browser. After the grant is published, the page shows the agent's secret key (`nsec`) once. Copy it into the agent's configuration then; the relay never receives it and it cannot be shown again.97+- **Paste a public key** grants an agent that already has a key.98+99+Add the rooms and kinds the agent may post in, one repository per line as `<owner pubkey>:<identifier>:read` or `:maintain`, wiki access, a rate and an expiry date. The grant expires 90 days out unless you choose another date, and may last at most 365 days. Fields the relay would refuse are reported before anything is signed. Publishing a grant for an agent that already has one replaces it.100+84101 ## Discovery85102 86103 While at least one agent is active, the relay's information document includes an `agents` capability entry, so clients and other agents can tell that this relay accepts granted agents. The entry carries no agent details.@@ -8,4 +8,18 @@ In Chrome, enable **WebMCP for testing** at `chrome://flags/#enable-webmcp-testi
88 99 Read the current policy or connection list before changing settings. Job intervals are measured in hours; zero runs once.1010 11+## Agents12+13+The owner and moderators can also manage [agent grants](agents.md) through the browser agent:14+15+| Tool | What it does |16+| --- | --- |17+| `tiny.list_agents` | Lists every agent with its name, public key, owner, scope, state, expiry and last event. Read-only; uses the connected signer. |18+| `tiny.read_agent` | Reads one agent's grant and its 10 newest events. Read-only; uses the browser session. |19+| `tiny.pause_agent` | Pauses an agent. The grant stays and its writes are rejected until it is resumed. |20+| `tiny.resume_agent` | Resumes a paused agent. |21+| `tiny.revoke_agent` | Revokes an agent's grant. Only a new grant restores its access. |22+23+Each control takes the agent's public key and requests a signature. Signing a new grant stays on the **Manage > Agents** page, since the secret key of a generated agent is shown to the person once.24+1125 Agents that run outside the browser use the same tools over the relay's MCP endpoint. See [MCP](mcp.md).