cade-cli 0.16.6__tar.gz → 0.16.7__tar.gz

{cade_cli-0.16.6 → cade_cli-0.16.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: cade-cli
-Version: 0.16.6
+Version: 0.16.7
 Summary: Cade - The CLI Agent from Arcade.dev (install: curl -fsSL https://arcadeagent.dev/install | sh)
 Project-URL: Homepage, https://arcade.dev
 Project-URL: Documentation, https://arcadeagent.dev/docs
@@ -111,7 +111,7 @@ toolchain. First `cade` walks you through model setup, Arcade login, and the
 - **Tools from anywhere.** Built-in local tools (filesystem / shell / git / search / tasks / memory), [Arcade Cloud](https://arcade.dev) tools (Slack, GitHub, Gmail, calendars, …), and any [MCP](https://modelcontextprotocol.io/) server you register — all unified under one tool surface.
 - **Bidirectional MCP.** Tools can call `context.ui.elicit(…)` for structured input, `context.log.*` for live operator logs, and `context.progress.report(…)` for editable progress UI — routed end-to-end through whichever adapter is active (Telegram inline keyboard, terminal prompt).
 - **Agents + per-agent memory.** Multiple agents, each with their own model, system prompt, tools, and an indexed memory store backed by [agent-library](https://pypi.org/project/agent-library/).
-- **Extensibility surface.** Hooks (lifecycle events), tasks (durable work), cron (scheduled prompts) — all available to the agent as `Local_*` tools and to you as `cade <subcommand>`.
+- **Extensibility surface.** Hooks (lifecycle events), tasks (durable work), cron (scheduled prompts) — all available to the agent as `Local_*` tools and to you as `cade agent hooks` / `tasks` / `cron`.
 - **Bring your own LLM.** OpenAI, Anthropic, or any OpenAI-compatible endpoint (Ollama, vLLM, Together, Groq, Fireworks, …). `--local-only` skips Arcade Cloud entirely.
 
 ---
@@ -129,7 +129,7 @@ The script detects your OS/arch, downloads the matching prebuilt binary
 `~/.local/bin`. Pin a version or install location:
 
 ```bash
-CADE_VERSION=0.16.6 CADE_INSTALL_DIR=/usr/local/bin \
+CADE_VERSION=0.16.7 CADE_INSTALL_DIR=/usr/local/bin \
   sh -c "$(curl -fsSL https://arcadeagent.dev/install)"
 ```
 
@@ -154,10 +154,10 @@ curl installer does **not** require a local Python — Python 3.11+ is only need
 for the uv / pip / from-source paths.
 
 The first run walks you through picking a model provider and key (stored in your
-OS keyring); re-run it any time with `cade init`.
+OS keyring); re-run it any time with `cade account init`.
 
 ```bash
-cade init           # pick provider + model (runs automatically on first launch)
+cade account init   # pick provider + model (runs automatically on first launch)
 cade login          # Arcade Cloud OAuth (skip with --local-only)
 cade --version
 ```
@@ -171,14 +171,18 @@ Full install and first-run docs: [`docs/install.md`](./docs/install.md) and
 
 ```bash
 cade                                       # interactive chat
+cade chat                                  # same
+cade chat -r                               # resume most recent thread
+cade chat --resume "auth-rewrite"          # resume a named thread
 cade -m "What changed in HEAD?"            # single message, then exit
 cade -m "What went wrong?" < error.log     # prompt + file/stdin
-cade resume                                # resume the most recent thread
-cade resume "auth-rewrite"                 # resume a thread by name
-cade use reviewer                          # switch the current agent
 cade --voice                               # speak / hear (requires cade-cli[voice])
 ```
 
+`cade --help` shows: `chat`, `agent`, `mcp`, `daemon`, `account`, `login`,
+`logout`. Tools are under `cade agent tools`. Older flat names (`cade list`,
+`cade mem`, `cade tools`, `cade resume`, …) still work as hidden aliases.
+
 ### Top-level options
 
 | Flag | Description |
@@ -198,7 +202,7 @@ cade --voice                               # speak / hear (requires cade-cli[voi
 | `/logs` | Recent log entries |
 | `/thread`, `/history` | Current thread info |
 | `/pin`, `/unpin` | Pin reference material into the session |
-| `/tasks`, `/cron`, `/hooks`, `/notify` | Coordination surfaces (mirrored as `cade tasks` / `cade cron` / `cade hooks`) |
+| `/tasks`, `/cron`, `/hooks`, `/notify` | Coordination surfaces (also `cade agent tasks` / `cron` / `hooks`) |
 | `/usage` | Context-window status and token usage |
 | `/cd`, `/pwd`, `/!` | Shell shortcuts |
 | `Ctrl+C` | Exit |
@@ -214,10 +218,10 @@ Tools come from three sources and are addressed uniformly by their registered na
 - **Arcade Agent Hub + user MCP servers** — Hub for Gmail/Slack/GitHub/… (`cade mcp authorize hub`); plus anything else you register.
 
 ```bash
-cade tools list                         # all tools, all sources
-cade tools list --source local          # filter by source
-cade tools search "send slack"          # keyword search
-cade tools info Local_ReadFile          # full schema + description
+cade agent tools list                   # MCP tools (Local_* hidden by default)
+cade agent tools list --source local    # built-in Local_* tools only
+cade agent tools search "send slack"    # keyword search
+cade agent tools info Local_ReadFile    # full schema + description
 cade mcp authorize hub                  # Arcade catalogue (OAuth)
 cade mcp install-hosts                  # register Cade in Cursor / Claude / …
 ```
@@ -230,7 +234,7 @@ The full local tool surface (including the bidirectional MCP capabilities and `c
 cade mcp add my-server http://localhost:8080
 cade mcp add my-server http://… --auth bearer -t <token>
 cade mcp authorize my-server                      # OAuth flow (browser)
-cade mcp list / status / test / enable / disable / rm
+cade mcp list / status / enable / disable / rm
 ```
 
 User MCP servers register on the agent's `~/.cade/config/agents/<name>.toml [[mcp]]` list (with `cade.toml [agent_defaults].mcp` as the shared default). Servers with large catalogs are auto-deferred (parameter schemas stripped to keep tool-list bytes down) and fetched on demand via `Local_ToolSchema`.
@@ -243,22 +247,22 @@ Each **agent** bundles a model, system prompt, tools, and memory. The current
 agent is ambient — most commands act on it.
 
 ```bash
-cade new reviewer --prompt "You are a meticulous code reviewer."  # create + switch
-cade list                                     # all agents
-cade use reviewer                             # switch the current agent
-cade info / cade edit reviewer                # inspect / change config
-
-cade mem                                      # the current agent's memory (status)
-cade mem add ~/notes                          # index a directory
-cade mem search "auth design"                 # semantic search
-cade mem warm                                 # pre-load the semantic memory model
+cade agent new reviewer --prompt "You are a meticulous code reviewer."
+cade agent list
+cade agent use reviewer
+cade agent info / cade agent edit reviewer
+
+cade agent mem                                # status
+cade agent mem add ~/notes
+cade agent mem search "auth design"
+cade agent mem warm                           # pre-load semantic search
 ```
 
 Memory is per-agent — each agent has its own
 `~/.cade/data/agents/<id>/memory/.librarian/` index, so a `reviewer` agent's
 notes never leak into another. Cade advertises `Memory_*` tools without starting
 the memory server; the first actual memory call starts it and keeps it warm for
-later calls. Use `cade mem warm` when you want to pay that semantic-search
+later calls. Use `cade agent mem warm` when you want to pay that semantic-search
 warmup before a conversation.
 
 ---
@@ -288,13 +292,12 @@ Three primitives the agent uses directly (as `Local_*` tools) and you can drive
 
 | Surface | What it is | CLI |
 |---|---|---|
-| **Hooks** | Lifecycle event handlers (pre/post tool, user prompt submit) | `cade hooks list / add / remove / test` |
-| **Tasks** | Durable work units that survive turn boundaries | `cade tasks list / get / create / update / delete` |
-| **Cron** | Scheduled prompts the agent runs on a timer | `cade cron list / add / remove / enable / disable / run-now` |
+| **Hooks** | Lifecycle event handlers (pre/post tool, user prompt submit) | `cade agent hooks …` |
+| **Tasks** | Durable work units that survive turn boundaries | `cade agent tasks …` |
+| **Cron** | Scheduled prompts the agent runs on a timer | `cade agent cron …` |
 
-Cross-agent messaging is set up with `cade link` / `cade channel` (an agent can only
-reach another it's been linked to). Hooks and tasks/cron details live in their
-respective `cade <subcommand> --help` outputs.
+Cross-agent messaging is set up with `cade agent link` / `cade agent channel`.
+See `cade agent --help` for the full surface.
 
 ---
 
@@ -307,8 +310,8 @@ Cade works with any OpenAI-compatible endpoint. Three ways to wire one in (CLI f
 cade chat -L --endpoint http://localhost:11434 --model qwen3:4b
 
 # Or create a dedicated agent for the local model
-cade new local-qwen --model qwen3:4b
-cade use local-qwen
+cade agent new local-qwen --model qwen3:4b
+cade agent use local-qwen
 export OLLAMA_BASE_URL="http://localhost:11434"
 CADE_LOCAL_ONLY=1 cade -m "hello from a local model"
 

{cade_cli-0.16.6 → cade_cli-0.16.7}/README.md

@@ -20,7 +20,7 @@ toolchain. First `cade` walks you through model setup, Arcade login, and the
 - **Tools from anywhere.** Built-in local tools (filesystem / shell / git / search / tasks / memory), [Arcade Cloud](https://arcade.dev) tools (Slack, GitHub, Gmail, calendars, …), and any [MCP](https://modelcontextprotocol.io/) server you register — all unified under one tool surface.
 - **Bidirectional MCP.** Tools can call `context.ui.elicit(…)` for structured input, `context.log.*` for live operator logs, and `context.progress.report(…)` for editable progress UI — routed end-to-end through whichever adapter is active (Telegram inline keyboard, terminal prompt).
 - **Agents + per-agent memory.** Multiple agents, each with their own model, system prompt, tools, and an indexed memory store backed by [agent-library](https://pypi.org/project/agent-library/).
-- **Extensibility surface.** Hooks (lifecycle events), tasks (durable work), cron (scheduled prompts) — all available to the agent as `Local_*` tools and to you as `cade <subcommand>`.
+- **Extensibility surface.** Hooks (lifecycle events), tasks (durable work), cron (scheduled prompts) — all available to the agent as `Local_*` tools and to you as `cade agent hooks` / `tasks` / `cron`.
 - **Bring your own LLM.** OpenAI, Anthropic, or any OpenAI-compatible endpoint (Ollama, vLLM, Together, Groq, Fireworks, …). `--local-only` skips Arcade Cloud entirely.
 
 ---
@@ -38,7 +38,7 @@ The script detects your OS/arch, downloads the matching prebuilt binary
 `~/.local/bin`. Pin a version or install location:
 
 ```bash
-CADE_VERSION=0.16.6 CADE_INSTALL_DIR=/usr/local/bin \
+CADE_VERSION=0.16.7 CADE_INSTALL_DIR=/usr/local/bin \
   sh -c "$(curl -fsSL https://arcadeagent.dev/install)"
 ```
 
@@ -63,10 +63,10 @@ curl installer does **not** require a local Python — Python 3.11+ is only need
 for the uv / pip / from-source paths.
 
 The first run walks you through picking a model provider and key (stored in your
-OS keyring); re-run it any time with `cade init`.
+OS keyring); re-run it any time with `cade account init`.
 
 ```bash
-cade init           # pick provider + model (runs automatically on first launch)
+cade account init   # pick provider + model (runs automatically on first launch)
 cade login          # Arcade Cloud OAuth (skip with --local-only)
 cade --version
 ```
@@ -80,14 +80,18 @@ Full install and first-run docs: [`docs/install.md`](./docs/install.md) and
 
 ```bash
 cade                                       # interactive chat
+cade chat                                  # same
+cade chat -r                               # resume most recent thread
+cade chat --resume "auth-rewrite"          # resume a named thread
 cade -m "What changed in HEAD?"            # single message, then exit
 cade -m "What went wrong?" < error.log     # prompt + file/stdin
-cade resume                                # resume the most recent thread
-cade resume "auth-rewrite"                 # resume a thread by name
-cade use reviewer                          # switch the current agent
 cade --voice                               # speak / hear (requires cade-cli[voice])
 ```
 
+`cade --help` shows: `chat`, `agent`, `mcp`, `daemon`, `account`, `login`,
+`logout`. Tools are under `cade agent tools`. Older flat names (`cade list`,
+`cade mem`, `cade tools`, `cade resume`, …) still work as hidden aliases.
+
 ### Top-level options
 
 | Flag | Description |
@@ -107,7 +111,7 @@ cade --voice                               # speak / hear (requires cade-cli[voi
 | `/logs` | Recent log entries |
 | `/thread`, `/history` | Current thread info |
 | `/pin`, `/unpin` | Pin reference material into the session |
-| `/tasks`, `/cron`, `/hooks`, `/notify` | Coordination surfaces (mirrored as `cade tasks` / `cade cron` / `cade hooks`) |
+| `/tasks`, `/cron`, `/hooks`, `/notify` | Coordination surfaces (also `cade agent tasks` / `cron` / `hooks`) |
 | `/usage` | Context-window status and token usage |
 | `/cd`, `/pwd`, `/!` | Shell shortcuts |
 | `Ctrl+C` | Exit |
@@ -123,10 +127,10 @@ Tools come from three sources and are addressed uniformly by their registered na
 - **Arcade Agent Hub + user MCP servers** — Hub for Gmail/Slack/GitHub/… (`cade mcp authorize hub`); plus anything else you register.
 
 ```bash
-cade tools list                         # all tools, all sources
-cade tools list --source local          # filter by source
-cade tools search "send slack"          # keyword search
-cade tools info Local_ReadFile          # full schema + description
+cade agent tools list                   # MCP tools (Local_* hidden by default)
+cade agent tools list --source local    # built-in Local_* tools only
+cade agent tools search "send slack"    # keyword search
+cade agent tools info Local_ReadFile    # full schema + description
 cade mcp authorize hub                  # Arcade catalogue (OAuth)
 cade mcp install-hosts                  # register Cade in Cursor / Claude / …
 ```
@@ -139,7 +143,7 @@ The full local tool surface (including the bidirectional MCP capabilities and `c
 cade mcp add my-server http://localhost:8080
 cade mcp add my-server http://… --auth bearer -t <token>
 cade mcp authorize my-server                      # OAuth flow (browser)
-cade mcp list / status / test / enable / disable / rm
+cade mcp list / status / enable / disable / rm
 ```
 
 User MCP servers register on the agent's `~/.cade/config/agents/<name>.toml [[mcp]]` list (with `cade.toml [agent_defaults].mcp` as the shared default). Servers with large catalogs are auto-deferred (parameter schemas stripped to keep tool-list bytes down) and fetched on demand via `Local_ToolSchema`.
@@ -152,22 +156,22 @@ Each **agent** bundles a model, system prompt, tools, and memory. The current
 agent is ambient — most commands act on it.
 
 ```bash
-cade new reviewer --prompt "You are a meticulous code reviewer."  # create + switch
-cade list                                     # all agents
-cade use reviewer                             # switch the current agent
-cade info / cade edit reviewer                # inspect / change config
-
-cade mem                                      # the current agent's memory (status)
-cade mem add ~/notes                          # index a directory
-cade mem search "auth design"                 # semantic search
-cade mem warm                                 # pre-load the semantic memory model
+cade agent new reviewer --prompt "You are a meticulous code reviewer."
+cade agent list
+cade agent use reviewer
+cade agent info / cade agent edit reviewer
+
+cade agent mem                                # status
+cade agent mem add ~/notes
+cade agent mem search "auth design"
+cade agent mem warm                           # pre-load semantic search
 ```
 
 Memory is per-agent — each agent has its own
 `~/.cade/data/agents/<id>/memory/.librarian/` index, so a `reviewer` agent's
 notes never leak into another. Cade advertises `Memory_*` tools without starting
 the memory server; the first actual memory call starts it and keeps it warm for
-later calls. Use `cade mem warm` when you want to pay that semantic-search
+later calls. Use `cade agent mem warm` when you want to pay that semantic-search
 warmup before a conversation.
 
 ---
@@ -197,13 +201,12 @@ Three primitives the agent uses directly (as `Local_*` tools) and you can drive
 
 | Surface | What it is | CLI |
 |---|---|---|
-| **Hooks** | Lifecycle event handlers (pre/post tool, user prompt submit) | `cade hooks list / add / remove / test` |
-| **Tasks** | Durable work units that survive turn boundaries | `cade tasks list / get / create / update / delete` |
-| **Cron** | Scheduled prompts the agent runs on a timer | `cade cron list / add / remove / enable / disable / run-now` |
+| **Hooks** | Lifecycle event handlers (pre/post tool, user prompt submit) | `cade agent hooks …` |
+| **Tasks** | Durable work units that survive turn boundaries | `cade agent tasks …` |
+| **Cron** | Scheduled prompts the agent runs on a timer | `cade agent cron …` |
 
-Cross-agent messaging is set up with `cade link` / `cade channel` (an agent can only
-reach another it's been linked to). Hooks and tasks/cron details live in their
-respective `cade <subcommand> --help` outputs.
+Cross-agent messaging is set up with `cade agent link` / `cade agent channel`.
+See `cade agent --help` for the full surface.
 
 ---
 
@@ -216,8 +219,8 @@ Cade works with any OpenAI-compatible endpoint. Three ways to wire one in (CLI f
 cade chat -L --endpoint http://localhost:11434 --model qwen3:4b
 
 # Or create a dedicated agent for the local model
-cade new local-qwen --model qwen3:4b
-cade use local-qwen
+cade agent new local-qwen --model qwen3:4b
+cade agent use local-qwen
 export OLLAMA_BASE_URL="http://localhost:11434"
 CADE_LOCAL_ONLY=1 cade -m "hello from a local model"
 

{cade_cli-0.16.6 → cade_cli-0.16.7}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "cade-cli"
-version = "0.16.6"
+version = "0.16.7"
 description = "Cade - The CLI Agent from Arcade.dev (install: curl -fsSL https://arcadeagent.dev/install | sh)"
 readme = "README.md"
 requires-python = ">=3.11"

{cade_cli-0.16.6 → cade_cli-0.16.7}/src/cade_mcp_local/resources.py

@@ -144,10 +144,10 @@ def register_resources(app: MCPApp, instructions: str) -> None:
     app.add_resource(
         MEMORY_SOURCES_URI,
         name="memory-sources",
-        title="cade mem sources (active persona)",
+        title="cade agent mem sources (active persona)",
         description=(
             "JSON listing of memory sources registered for the active persona "
-            "(equivalent to `cade mem sources`). Read each call so the listing "
+            "(equivalent to `cade agent mem sources`). Read each call so the listing "
             "reflects sources added after server start."
         ),
         mime_type="application/json",

{cade_cli-0.16.6 → cade_cli-0.16.7}/src/cade_mcp_local/tools/access.py

@@ -8,7 +8,7 @@ added to the live :class:`~cade_mcp_local.grants.GrantSet` (session-scoped)
 and every subsequent tool call — typed file tools and ``Local_Bash`` alike —
 sees it immediately via the mtime-cached grants file. Without elicitation the
 tool returns a denial explaining the operator must run ``/grant`` (or
-``cade grant``) manually.
+``cade agent grant``) manually.
 """
 
 import logging
@@ -99,7 +99,7 @@ async def request_access_tool(
             "mode": mode,
             "message": (
                 f"Cannot request consent on this surface. Ask the operator to "
-                f"run `/grant {resolved} {mode}` (or `cade grant`)."
+                f"run `/grant {resolved} {mode}` (or `cade agent grant`)."
             ),
             "scopes": grant_set.describe(),
         }

{cade_cli-0.16.6 → cade_cli-0.16.7}/src/cade_mcp_local/tools/agents.py

@@ -3,7 +3,7 @@
 Lets the model address other agents the user has explicitly linked. Delivery
 rides the durable per-agent inbox (so the message survives until the target
 agent's next turn), and the user-provisioned channel ACL gates every send:
-two top-level agents can talk only if a user ran ``cade link`` / added them to
+two top-level agents can talk only if a user ran ``cade agent link`` / added them to
 a shared channel. The default is isolation.
 """
 
@@ -68,7 +68,7 @@ def _current_agent_name() -> str:
     name="AgentSend",
     desc=(
         "Send a message to another agent's inbox. Only works for agents a user "
-        "has linked to this one (via `cade link` or a shared channel); otherwise "
+        "has linked to this one (via `cade agent link` or a shared channel); otherwise "
         "the send is refused. The message is delivered at the target agent's next "
         "turn. Use AgentList first to see who you can reach."
     ),
@@ -115,7 +115,7 @@ async def agent_send_tool(
         raise InvalidInputError(
             "target",
             f"not linked with '{target_agent.name}'. A user must run: "
-            f"cade link {sender} {target_agent.name}",
+            f"cade agent link {sender} {target_agent.name}",
         )
     inbox = inbox_for_path(get_paths().agent_data(target_agent.id))
     inbox.enqueue_notification(message, source=f"agent:{sender}")