@grepr/cli 1.12.5-302149d → 1.12.6-043e074

package/build/dist/docs-index/{4f1f8da6-bb44-425f-a1e0-e4ed507a47a4.txt → eefd4dc0-53a6-4a65-bd0f-a1ca86d27d7a.txt}

@@ -79,7 +79,9 @@ An agent's pipeline changes are scoped to a pipeline's Grok parsers and its SQL
 
 A SQL transform an agent adds is a filter and nothing further. It reads the pipeline's logs and selects them unchanged against a single condition, so it cannot join, aggregate, read a dataset, register a function, or keep state. It routes the events it matches to the agent signal sink, which you configure yourself when you set the pipeline up. An agent can add routes to that sink, and it cannot create, change, or remove the sink. That limit is on what an agent adds by itself. A SQL output you route to the agent signal sink yourself carries no such restriction, so you can build the event an agent receives however you need. See [_](/ai-agents/subscriptions#agent-signal-sink).
 
-The tools an agent uses with memories and issues are not in this list. Every agent can search and read both, and the **Remember past investigations** and **Works on issues** switches in the **Memory and issues** section decide whether it also records memories and changes issues. See [_](/ai-agents/memory).
+The tools and skills you grant also decide which `grepr` CLI commands the agent can run.
+
+The tools an agent uses with memories and issues are not in this list. Every agent can search and read both. The **Remember past investigations** switch, on the agent's **Memories** step, and the **Works on issues** switch, on its **Issues** step, decide whether it also records memories and changes issues. When you create an agent, both are in the wizard's **Memory and issues** section. See [_](/ai-agents/memory) and [_](/ai-agents/issue-board).
 
 ## Let an agent call an MCP server's tools \[#mcp-integrations]
 

package/build/dist/docs-index/{cbe27c7e-d3f3-40ef-b0ef-46da7efc6aa9.txt → f6f3eee1-71cc-4855-9fc1-1f764b9a8d8d.txt}

@@ -34,7 +34,7 @@ Investigations are long-running and tool-heavy, so the model you choose changes
 
 The **Capabilities** step is where you choose the service account the agent acts as, the tools and skills it can use, the MCP servers it can call, and whether the pipeline changes it proposes need your approval. To learn more, see [_](/ai-agents/capabilities).
 
-The step ends with the **Memory and issues** section, which is collapsed. Every new agent records memories and works on issues, so open the section to turn off **Remember past investigations** or **Works on issues**, to set the store for searching memories by meaning, or to choose **Allow Ready** so the agent can file issues in Ready and move issues there. Every agent can search and read memories and issues, whichever switches are on. To learn more about memory, see [_](/ai-agents/memory). To learn more about how agents work on issues and pick up Ready issues, see [_](/ai-agents/issue-board).
+The step ends with the **Memory and issues** section, which is collapsed. Every new agent records memories and works on issues, so open the section to turn off **Remember past investigations** or **Works on issues**, to set the store for searching memories by meaning, or to choose **Allow Ready** so the agent can file issues in Ready and move issues there. Every agent can search and read memories and issues, whichever switches are on. After the agent exists, these settings are on its **Memories** and **Issues** steps. To learn more about memory, see [_](/ai-agents/memory). To learn more about how agents work on issues and pick up Ready issues, see [_](/ai-agents/issue-board).
 
 ### Step 4: Subscribe to signal sources \[#step4-subscriptions]
 
@@ -106,10 +106,11 @@ When a token budget is exhausted, new investigations stop starting and resume wh
 An agent's settings are spread across the steps on its page, which hold the same fields as the wizard:
 
 * **Behavior** holds the name, the system prompt, the model, and the limits.
-* **Capabilities** holds the service account, the tools, the skills, the MCP integrations, the change approval mode, and the **Memory and issues** section, which holds whether the agent works on issues.
+* **Capabilities** holds the service account, the tools, the skills, the MCP integrations, and the change approval mode.
 * **Memories** holds the memory settings and, below them, the memories the agent recorded.
+* **Issues** holds whether the agent works on issues, whether it can put issues in **Ready**, and which **Ready** issues it picks up. See [_](/ai-agents/issue-board).
 
-Changes to the settings on these three steps are held until you click **Save Changes**, so you can revise several steps in one pass. To abandon them, click **Discard Changes**. Subscriptions are not part of this and apply as soon as you make them. Neither are changes to individual memories on the **Memories** step: an edit, a verdict, or a delete applies as soon as you confirm it, and **Discard Changes** does not undo it.
+Changes to the settings on these four steps are held until you click **Save Changes**, so you can revise several steps in one pass. To abandon them, click **Discard Changes**. Subscriptions are not part of this and apply as soon as you make them. Neither are changes to individual memories on the **Memories** step: an edit, a verdict, or a delete applies as soon as you confirm it, and **Discard Changes** does not undo it.
 
 An investigation reads the agent's instructions, model, and limits when it starts, so correcting those mid-incident leaves the current run on the settings it began with and applies to the next one.