Portfolio vs Client Ops

Two jobs get mixed up if you give one worker both. Client Ops serves a single client site. Portfolio looks across sites for an operator or agency. They share Docs. They do not share a key.

What each is for

Client Ops is the worker on one site. It reads that site's Requests and, when the Knowledge Base ships, that site's facts. It drafts. A person reviews. Missing facts escalate. It does not wander into another customer's dashboard.

Portfolio is the operator watcher. It looks across many sites. Coming soon, that view should show whether Knowledge Base categories have facts, not the brand paragraphs themselves. Coverage is not a second editor. Portfolio does not draft client copy.

• Client Ops: one site, one key, Request work on that site.
• Portfolio: one listing for the agency, completeness across sites.
• If a site needs a change, that work still files as a Request on that site and follows Servicing requests.

Portfolio does not draft

A Portfolio view should not write client copy. Keep GitHub and the host in the developer lane. Owners still review Looks good. Someone who is allowed still asks to Ship to live.

Add Portfolio once

The operator or agency adds Portfolio once. Do not clone a new Portfolio listing for every client. One Portfolio watcher is enough for the people who watch many sites.

• Portfolio (Commander on the storefront): https://x.ai/bot/9Y85rjk95hWiH41N4BfP-
• Add it once for the agency, not once per site.

Duplicate Client Ops per site

Client Ops is per site. Duplicate the listing once for each client site you serve. Each copy gets its own worker key. Never stretch one Client Ops worker across two customers.

• Client Ops: https://x.ai/bot/4w4Fh6McLeeaGUmtWKb9M
• Duplicate, then name the copy for that site.
• Mint a worker key on that site only.

1. Open the Client Ops listing.
2. Duplicate it for the site you are connecting.
3. Mint a worker key on that site in Settings, Requests.
4. Add the wake URL on the same card if you use wake.
5. Point the worker at Docs. Do not paste this handbook into memory.

Then connect with a worker key and wake

After you add or duplicate a listing, connect it the way the product works today: a site-scoped worker key and an optional wake webhook. That is the live door. See Gateway, APIs, and MCP.

Interactive MCP OAuth (OAuth 2.1 and PKCE) is Coming soon. It does not replace wake. When that approve screen ships, Connect an agent (MCP) will name the URLs. Do not invent them in a listing.

Marketplace listings

These two listings are the canonical starts. Open them, then follow Add Portfolio once and Duplicate Client Ops per site. Do not treat a slide as a catalog.

• Portfolio: https://x.ai/bot/9Y85rjk95hWiH41N4BfP-
• Client Ops: https://x.ai/bot/4w4Fh6McLeeaGUmtWKb9M

Read Docs first

When you wire a worker, give it these URLs. Do not copy the whole stack into bot memory and hope it stays current. The handbook is the source.

• How xTerminal works: /xterminal/docs/how-xterminal-works
• The Request loop: /xterminal/docs/the-request-loop
• Servicing requests: /xterminal/docs/servicing-requests
• Knowledge Base: /xterminal/docs/knowledge-base
• Agents and the Knowledge Base: /xterminal/docs/agents-and-the-knowledge-base
• Gateway, APIs, and MCP: /xterminal/docs/gateway-apis-mcp
• Connect an agent (MCP): /xterminal/docs/connect-an-agent-mcp

What this is not

Not a shared robot across every site you own. Not an unsupervised publisher. Not a prompt box that emits a new site. See Agents as employees.