Skip to main content

Tools, Approvals, And Terminal

Tools are actions Row-Bot can take beyond writing text. They can search documents, read files, use a browser, run Developer commands, create designs, inspect knowledge, call MCP servers, use plugins, or send through channels.

How Tool Use Appears​

When Row-Bot uses a tool, the transcript can show a tool trace or result block. Read it as an activity receipt: what Row-Bot tried, what came back, and whether more action is needed.

Approval Prompts​

Approval prompts appear when an action can change local files, run commands, contact external systems, use accounts, start servers, send messages, call MCP/plugin tools, or do something else that deserves review.

If a child agent needs approval, Row-Bot posts a compact approval prompt in the parent thread, keeps the desktop Activity Center in sync, and routes channel-started work back to the originating channel when possible. The prompt may include a short model-written reason, but Row-Bot's approval policy still decides whether the action is blocked, allowed, or waiting for you.

Before approving, check:

  • What action is being requested.
  • What file, workspace, account, channel, server, or provider is involved.
  • Whether the action can send data outside the app.
  • Whether the proposed command or file change matches your request.
  • Whether rejecting is safer until you inspect settings.

Approving lets Row-Bot continue that action. Rejecting stops that action and returns control to the conversation. On small screens and in channels, prompts stay brief; open the thread or Activity Center when you need more context.

Terminal Output​

The terminal panel shows command-style output when Row-Bot surfaces it from local tools, Developer Studio, or related runtime activity. It is a review surface, not permission by itself. Commands still follow workspace boundaries, tool availability, and approval mode.

Common Workflow​

  1. Ask for a task that may need tools.
  2. Let Row-Bot explain the intended action.
  3. Review the approval prompt.
  4. Approve only if the action matches your intent.
  5. Inspect the tool trace or terminal output.
  6. Ask Row-Bot to summarize what changed.

Troubleshooting​

  • If no approval appears, the action may be read-only or blocked before execution.
  • If a tool result is confusing, ask Row-Bot to explain the last tool call.
  • If command output is missing, check whether you are in Developer Studio or a tool-capable context.
  • If you rejected by mistake, ask Row-Bot to try again and review the next prompt.