@rosthq/cli 0.5.10 → 0.5.11

package/dist/index.js

@@ -42180,7 +42180,7 @@ Review the first dry runs, fleet overview, tool-call audit rows, escalations, an
     order: 46,
     title: "Tool access and vault",
     summary: "How to give agents access to tools without exposing raw credentials or expanding authority by accident.",
-    version: "2026-06-20.1",
+    version: "2026-06-20.2",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing"],
@@ -42222,7 +42222,7 @@ Connecting a tool is a human-controlled step. The agent can recommend a tool, ex
 
 ## Generic REST connector
 
-For an API with no dedicated connector, the generic REST tool lets a seat call an HTTP endpoint with a credential you paste through the vault \u2014 no {{brand}}-owned app. It is escalate-by-default: the agent may only call a host a steward has signed onto the allowlist; any other host is refused and escalated, with no request made. The connector sets the Authorization header from the vaulted credential itself \u2014 the agent never sees the token, and the secret is redacted from the response before it reaches the agent, the audit row, or the logs. The token is only ever sent over HTTPS, only to the signed host, and a redirect is never followed \u2014 so an allowlisted endpoint cannot bounce the call (and the token) to another host. A sandbox dry run of a REST tool makes no real request.
+For an API with no dedicated connector, the generic REST tool lets a seat call an HTTP endpoint with a credential you paste through the vault \u2014 no {{brand}}-owned app. It is escalate-by-default: the agent may only call a host, method, and explicit path prefix a steward has signed onto the allowlist; any other host, method, or path is refused and escalated, with no request made. A path prefix of \`/\` means the steward intentionally approved every path. The connector sets the Authorization header from the vaulted credential itself \u2014 the agent never sees the token, and the secret is redacted from the response before it reaches the agent, the audit row, or the logs. The token is only ever sent over HTTPS, only to the signed host and scoped path, and a redirect is never followed \u2014 so an allowlisted endpoint cannot bounce the call (and the token) to another host. A sandbox dry run of a REST tool makes no real request.
 
 ## Slack post connector
 
@@ -42256,7 +42256,7 @@ There is exactly one way to give a connected tool its credential, and it is the
     order: 47,
     title: "Available tools guide",
     summary: "How to think about tool categories available to seats and what each category should be used for.",
-    version: "2026-06-20.1",
+    version: "2026-06-20.2",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing"],
@@ -42298,14 +42298,14 @@ Agents should explain the job, the required tool category, the minimum permissio
 
 Every tool call passes the server-side guard first: the guard checks the call against the seat's signed permission manifest and records a tool-call audit row for **every** call \u2014 allowed, denied, or escalated. Tool selection is never authorization. Only an allowed call reaches its handler. A connected credential is bound into the handler for the duration of the call only; the secret never appears in the result, the audit summary, logs, or the model's context.
 
-External connectors are being rolled out provider by provider, conservatively (read and draft before send; write behind approval). A selected tool is only a permission until a live handler exists and the seat has the required credential or binding. Today the built-in execution path supports internal status reporting, the generic REST connector when a signed allowlist and credential exist, and \`slack.post_message\` for a bound Slack channel. Other provider entries remain configuration-only until their connector ships, so nothing runs silently.`
+External connectors are being rolled out provider by provider, conservatively (read and draft before send; write behind approval). A selected tool is only a permission until a live handler exists and the seat has the required credential or binding. Today the built-in execution path supports internal status reporting, the generic REST connector when a signed host/method/path allowlist and credential exist, and \`slack.post_message\` for a bound Slack channel. Other provider entries remain configuration-only until their connector ships, so nothing runs silently.`
   },
   {
     slug: "mcp-and-cli-guide",
     order: 48,
     title: "CLI and MCP installation guide",
     summary: "Install the public CLI, register remote token-backed MCP clients, and find the full command and tool catalog.",
-    version: "2026-06-20.2",
+    version: "2026-06-20.3",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["company_setup", "staffing"],
@@ -42721,6 +42721,7 @@ These ergonomic wrappers (including the \`{{cli}} agent\` group) require **{{cli
 | \`{{cli}} member invite|update|remove\` | \`member.invite\`, \`member.update\`, \`member.remove\` | Manage tenant members. | Tenant | \`{{cli}} member invite --email ops@example.com --role member\` |
 | \`{{cli}} agent templates|create|setup|tools|dry-run|go-live|status|run-now|get-run|show\` | \`agent_template.list\`, \`agent.create_from_template\`, \`agent.create_custom\`, \`agent_setup.get\`, \`agent_setup.update\`, \`agent.configure_tools\`, \`agent.run_dry_run\`, \`agent.go_live\`, \`agent.status\`, \`agent.run_now\`, \`agent.get_run\`, \`agent.show_markdown\` | Run the full agent setup and operation flow: list templates, create a draft from a template or guided custom answers (with \`--model\` and \`--effort\`), read or answer setup state, connect or decline tools, dry-run, go live, run on demand, read one run's transcript/error diagnostics, and show a markdown readout. Create and go-live stop at human gates; the dry-run is ungated by human approval but requires a signed manifest first. | Tenant and seat | \`{{cli}} agent get-run --seat-id <seat-id> --run-id <run-id> --json\` |
 | \`{{cli}} tools list\` | \`tool.catalog\` | List the discoverable tool catalog the builder reads (id, scope tiers, credential requirement, access policy, and execution-boundary guidance). | Tenant | \`{{cli}} tools list --json\` |
+| \`{{cli}} model list\` | \`model.catalog\` | List guided model tiers with recommendations, token prices, cost bands, best-fit work, and model ids for \`--model\`. | Tenant | \`{{cli}} model list --json\` |
 | \`{{cli}} compass show\` | \`compass.show_markdown\` | Render the current Compass as a clean markdown card for review. | Tenant | \`{{cli}} compass show --markdown\` |
 | \`{{cli}} charter show\` | \`charter.show_markdown\` | Render a seat's Charter as a clean markdown card for review. | Tenant | \`{{cli}} charter show --seat-id <id> --markdown\` |
 
@@ -42743,7 +42744,8 @@ This catalog is the canonical machine surface \u2014 the \`rost_*\` tools your M
 
 1. **The MCP tools below** \u2014 the \`rost_*\` surface your client actually calls to read and act.
 2. **\`{{cli}} tools list\` / \`tool.catalog\`** (MCP \`rost_list_tool_catalog\`) \u2014 the agent-configuration catalog the builder reads when staffing an agent. It is selectable per agent, but selecting a tool is not itself a call; live handlers execute later only behind the signed manifest, guard, credentials, and bindings.
-3. **The "Available tools guide"** (in the sidebar) \u2014 covers tool *categories* and governance, not a callable surface. See the available-tools-guide.
+3. **\`{{cli}} model list\` / \`model.catalog\`** (MCP \`rost_list_model_catalog\`) \u2014 the guided model-tier catalog the builder reads for recommendations, effort, token prices, cost bands, and model id selection.
+4. **The "Available tools guide"** (in the sidebar) \u2014 covers tool *categories* and governance, not a callable surface. See the available-tools-guide.
 
 Sections below: Command discovery (2) \xB7 Public reference (3) \xB7 Tenant-admin tools (grouped by domain) \xB7 Seat-scoped operating tools (9) \xB7 MCP operation resources (9).
 
@@ -42879,6 +42881,7 @@ Several rows here are seat-operating commands (\`task.create\`, the \`signal.*\`
 | \`rost_show_charter_as_markdown\` | \`charter.show_markdown\` | Render a seat's active or latest Charter as a clean markdown card for review. | Tenant | Call with \`{"seat_id":"<seat-id>"}\`. |
 | \`rost_show_agent_setup_as_markdown\` | \`agent.show_markdown\` | Render a seat's agent setup, model, steward, tools, and Charter as a clean markdown card for review. | Tenant | Call with \`{"seat_id":"<seat-id>"}\`. |
 | \`rost_list_tool_catalog\` | \`tool.catalog\` | List the discoverable tool catalog the agent builder reads \u2014 id, prescriptive description, scope tiers, credential requirement, access policy, and execution-boundary guidance. | Tenant | Call with \`{}\` or \`{"provider":"google"}\`. |
+| \`rost_list_model_catalog\` | \`model.catalog\` | List guided model tiers \u2014 recommendations, token prices, cost bands, best-fit work, and model ids for \`--model\`. | Tenant | Call with \`{}\`. |
 
 ### Seat-scoped operating tools
 
@@ -42936,7 +42939,7 @@ These rows are quick, at-a-glance triage. For deeper auth, tenant, scope, confir
     order: 49,
     title: "Agent reference map",
     summary: "Where CLI sessions, MCP clients, and in-app agents should retrieve {{brand}} guidance before recommending setup changes.",
-    version: "2026-06-20.1",
+    version: "2026-06-20.2",
     public: true,
     audiences: ["cli", "mcp", "in_app_agent"],
     stages: ["company_setup", "graph_design", "charter_design", "staffing", "operating_rhythm"],
@@ -42987,6 +42990,7 @@ Never guess a command's JSON shape. Before calling a command that changes state,
 - List every callable command: {{cli}} command list (CLI) or rost_list_commands (MCP)
 - Read one command's exact input/output schema, help pointer, and a worked example: {{cli}} command schema <id> (CLI) or rost_describe_command with {"command_id":"<id>"} (MCP)
 - List the tool catalog the agent builder reads (id, scope tiers, credential requirement, access policy, and execution-boundary guidance): {{cli}} tools list (CLI) or rost_list_tool_catalog (MCP)
+- List guided model tiers before choosing --model (recommended default, effort, token prices, cost bands, best-fit work, model id): {{cli}} model list (CLI) or rost_list_model_catalog (MCP)
 - Show a Compass, Charter, or agent setup as a markdown card to review with your human: {{cli}} compass show --markdown, {{cli}} charter show --seat-id <id> --markdown, {{cli}} agent show --seat-id <id> --markdown
 
 When a command fails, the error returns a machine-readable code, a message, and a help field naming the exact command to run next. Read the help field and run the command it points at \u2014 do not retry the same call blindly. A failed precondition (for example a manifest not yet signed, a dry run that has not passed, or the inference budget hard cap reached) returns COMMAND_PRECONDITION_FAILED with a help pointer, not an opaque internal error.
@@ -43029,7 +43033,7 @@ Read the listed guide before recommending or running each workflow. Every workfl
 - Add an agent through the app (graph or sidebar, visual journey): add-agents-guide.
 - Create an agent from a template: stock-agents-guide, then how-agents-work.
 - Create a custom agent (operational answers, Charter Builder, configure tools, dry run, go live): custom-agents-guide, then agent-staffing-playbook and tool-access-and-vault.
-- Build a controlled agent worker directly on the CLI/MCP path (seat, steward, job, boundaries, tools, credentials, model, schedule, dry-run, go-live): agent-builder-guide \u2014 it shows the full setup sequence, the structured model config, the access tiers, how to discover tools (tool.catalog), which connector entries have live execution boundaries, and how to show your human a markdown readout (agent.show_markdown).
+- Build a controlled agent worker directly on the CLI/MCP path (seat, steward, job, boundaries, tools, credentials, model, schedule, dry-run, go-live): agent-builder-guide \u2014 it shows the full setup sequence, the structured model config, the model catalog (model.catalog), the access tiers, how to discover tools (tool.catalog), which connector entries have live execution boundaries, and how to show your human a markdown readout (agent.show_markdown).
 - Connect an existing or local agent to a seat: stock-agents-guide (connect section), then mcp-and-cli-guide and runner-guide.
 - Run the operating loop as a seat (context, tasks, status, escalate): how-agents-work.
 - Track goals: cascade-guide. Track measurables: signal-guide. File and resolve issues, tasks, escalations: friction-guide.
@@ -43735,7 +43739,7 @@ Name the failing surface, collect evidence, recommend the smallest correction, a
     order: 78,
     title: "Security model guide",
     summary: "How {{brand}} protects tenant data, credentials, tool calls, and human decisions across web, MCP, CLI, and agents.",
-    version: "2026-06-13.1",
+    version: "2026-06-20.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["company_setup", "staffing", "operating_rhythm"],
@@ -43766,6 +43770,8 @@ Name the failing surface, collect evidence, recommend the smallest correction, a
 - Agents recommend and draft; humans approve durable decisions.
 - Accepted knowledge changes by supersession, not silent mutation.
 
+The public Privacy Policy and Terms of Service are available at \`/privacy\` and \`/terms\` before sign-in and from the authenticated app chrome.
+
 ## Agent guidance
 
 Never infer permission from the user's wording or a locally available tool. Check the Charter, manifest, and server response. When in doubt, escalate with the evidence and the narrow question a human must decide.`
@@ -44067,7 +44073,7 @@ This worked document **omits** \`unanswered_boundaries\` and \`seat_type_recomme
     order: 43,
     title: "Agent builder guide",
     summary: "The full agent setup sequence on the CLI/MCP path \u2014 seat, steward, job, boundaries, tools, credentials, model, schedule, dry-run, go-live \u2014 with the structured model config and access tiers.",
-    version: "2026-06-20.1",
+    version: "2026-06-20.2",
     public: true,
     audiences: ["cli", "mcp", "in_app_agent"],
     stages: ["staffing"],
@@ -44078,6 +44084,7 @@ This worked document **omits** \`unanswered_boundaries\` and \`seat_type_recomme
       "agent_setup.update",
       "agent.configure_tools",
       "tool.catalog",
+      "model.catalog",
       "agent.run_dry_run",
       "agent.go_live",
       "agent.show_markdown",
@@ -44116,7 +44123,7 @@ Building teams of controlled agent workers is the product's core differentiator.
 5. **Tools** \u2014 pick from the discoverable catalog (\`{{cli}} tools list\`); each tool has a default scope tier and access policy. Connect or decline via \`agent.configure_tools\`. Selecting a tool records permission; live handlers execute later only behind the signed manifest, server guard, required credential or binding, and connector-specific approval boundary.
 6. **Credentials** \u2014 a tool that needs access declares a credential-ingress request (provider, scope, secret name). The secret itself flows through the vault-backed ingress command as a vault ref \u2014 never paste a secret into a builder command.
 7. **Operating instructions** \u2014 the runtime composes the agent's context from its Charter; you do not write a system prompt.
-8. **Model** \u2014 select the structured model config (see below).
+8. **Model** \u2014 select the structured model config (see below). Read \`{{cli}} model list\` / \`model.catalog\` first when you are unsure; it returns the recommended default, effort, token price estimates, cost band, and best-fit work for each tier. If \`agent.create_custom\` omits \`model_config\`, {{brand}} recommends a tier from the supplied responsibility answers.
 9. **Heartbeat** \u2014 set the schedule (\`schedule_cron\`) for a recurring agent; a live scheduled agent must keep a steward chain.
 10. **Dry-run** \u2014 \`agent.run_dry_run\` rehearses in sandbox after the manifest is signed; it is ungated by human approval but requires a signed manifest.
 11. **Go-live** \u2014 \`agent.go_live\` is \`human_required\`. Prepare everything and surface the go-live to a human; never go live on a human's behalf.
@@ -44133,6 +44140,8 @@ The agent's model is a structured object, not a bare string:
 - \`model\` is a model id. Pick by the work the seat does \u2014 a triage tier for cheap, high-volume classification; a balanced tier for most seats; a complex tier for judgment-heavy reasoning; the hardest tier for long-horizon agentic work. The builder offers tier shortcuts (\`triage\`, \`balanced\`, \`complex\`, \`hardest\`) that map to a current Claude id, so you never hardcode a stale one.
 - \`effort\` (\`low\` \u2192 \`max\`) trades thoroughness for cost/latency. Low for triage; high or xhigh for the hardest agentic seats.
 
+Run \`{{cli}} model list\` (MCP \`rost_list_model_catalog\`) before choosing when cost or reasoning depth is unclear. Balanced is the recommended default. Token prices are catalog estimates per million tokens, and cost bands are planning guidance for relative spend; the billing-grade number is still each run's recorded token usage and \`cost_usd\`. Custom agent creation recommends a tier from responsibility answers when \`model_config\` is omitted.
+
 On the CLI, \`{{cli}} agent create --custom --seat-id <id> --model balanced --effort medium \u2026\`, or set it later with \`{{cli}} agent setup answer --seat-id <id> --model complex\`. The model cannot change after the agent is live.
 
 ## Access tiers
@@ -45088,7 +45097,7 @@ function markdownLine(output) {
   const markdown = asRecord(output).markdown;
   return typeof markdown === "string" ? markdown : JSON.stringify(output, null, 2);
 }
-var MODEL_TIER_MAP = {
+var CLI_MODEL_TIER_MAP = {
   triage: { model: "claude-haiku-4-5", effort: "low" },
   balanced: { model: "claude-sonnet-4-6", effort: "medium" },
   complex: { model: "claude-opus-4-8", effort: "high" },
@@ -45098,7 +45107,7 @@ function resolveModelConfig(model, effort) {
   if (model === void 0) {
     return void 0;
   }
-  const tier = MODEL_TIER_MAP[model];
+  const tier = CLI_MODEL_TIER_MAP[model];
   const resolvedModel = tier ? tier.model : model;
   const resolvedEffort = effort ?? tier?.effort;
   return {
@@ -45945,6 +45954,44 @@ function toolsUsage(bin) {
   return `Usage: ${bin} tools list [--provider <name>] [--json]
   ${bin} tools list \u2014 the discoverable tool catalog the builder reads; live handlers execute only behind signed manifests, guards, credentials, and bindings.`;
 }
+var modelWrapper = (context, args) => dispatch(context, "model", args, {
+  list: (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    return execute(ctx, parsed, "model.catalog", {}, (output) => {
+      const record2 = asRecord(output);
+      const tiers = asArray(record2.tiers);
+      const header = `# Model tiers
+
+${field(record2, "note")}
+`;
+      if (tiers.length === 0) {
+        return `${header}
+No model tiers are configured.`;
+      }
+      const defaultTier = field(record2, "default_tier");
+      const lines = tiers.map((entry) => {
+        const r = asRecord(entry);
+        const tier = field(r, "tier");
+        const recommended = r.recommended === true || tier === defaultTier ? " recommended" : "";
+        const bestFor = asArray(r.best_for).map(String).join(", ");
+        return [
+          `- \`${tier}\` [${field(r, "provider")}/${field(r, "model")} \xB7 effort ${field(r, "effort")} \xB7 cost ${field(r, "cost_band")}${recommended}]`,
+          `  ${field(r, "description")}`,
+          `  Best for: ${bestFor}`,
+          `  Price: $${field(r, "input_usd_per_million_tokens")}/1M input \xB7 $${field(r, "output_usd_per_million_tokens")}/1M output`,
+          `  Cost: ${field(r, "cost_note")}`,
+          `  Avoid for: ${field(r, "avoid_for")}`
+        ].join("\n");
+      });
+      return `${header}
+${lines.join("\n")}`;
+    });
+  }
+}, modelUsage(context.binName));
+function modelUsage(bin) {
+  return `Usage: ${bin} model list [--json]
+  ${bin} model list \u2014 guided model tiers with recommendations, token prices, cost bands, and model ids for --model.`;
+}
 var compassWrapper = (context, args) => dispatch(context, "compass", args, {
   show: (ctx, rest) => {
     const parsed = parseFlags(rest, /* @__PURE__ */ new Set(["markdown"]));
@@ -45980,6 +46027,7 @@ var OPERATION_GROUPS = [
   "member",
   "agent",
   "tools",
+  "model",
   "compass",
   "charter"
 ];
@@ -45997,6 +46045,7 @@ var wrappers = {
   member: memberWrapper,
   agent: agentWrapper,
   tools: toolsWrapper,
+  model: modelWrapper,
   compass: compassWrapper,
   charter: charterWrapper
 };
@@ -46017,6 +46066,7 @@ var groupUsageBuilders = {
   member: memberUsage,
   agent: agentUsage,
   tools: toolsUsage,
+  model: modelUsage,
   compass: compassUsage,
   charter: charterUsage
 };
@@ -46046,6 +46096,7 @@ function operationUsageLines(bin) {
     `${bin} member invite|update|remove`,
     `${bin} agent templates|create|setup|tools|dry-run|go-live|status|run-now|get-run|show`,
     `${bin} tools list`,
+    `${bin} model list`,
     `${bin} compass show`,
     `${bin} charter show`
   ];