Skip to content

docs: document tool executions in the Operate area - #1129

Open
evantahler wants to merge 3 commits into
mainfrom
add-doc-screenshots
Open

docs: document tool executions in the Operate area#1129
evantahler wants to merge 3 commits into
mainfrom
add-doc-screenshots

Conversation

@evantahler

@evantahler evantahler commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Adds a Tool Executions page under Operate → Governance, next to Audit Logs, documenting the dashboard surface and read API shipped in ArcadeAI/monorepo#2661 and #2662.

The page covers both jobs the feature exists for: a developer debugging why a tool call failed by reading the exact inputs and outputs, and an operator reviewing what a project ran for compliance and usage. It documents the access split those PRs introduced — the history is readable by anyone holding a role on the project, while the recorded inputs and outputs take project-admin authority, and diagnostics stay readable either way — plus the dashboard filters, the three read endpoints, and the retention window.

Also adds three dashboard screenshots, cross-links the page from the developer-facing tool error handling guide, and adds it to the Governance and Operate card grids.

Verified with pnpm lint, pnpm test (835 pass), pnpm check-meta, Vale (0 errors), and a local dev-server render of the new page and both card grids.

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only changes with no runtime or security logic; low risk aside from ensuring API paths and permission descriptions stay aligned with the shipped product.

Overview
Adds a new Tool Executions doc under Operate → Governance that explains how to review recorded tool runs in the dashboard and via the read API—filters, attempt-level errors, debugging workflows, compliance-style usage review, admin-only inputs/outputs, retention, and the three tool_executions endpoints.

Navigation and discoverability: Registers the page in governance _meta, adds cards on the Governance and Operate overview pages, updates governance copy to mention tool runs alongside audit logs, links from the tool error handling guide to post-mortem debugging, and lists the page in public/llms.txt.

Reviewed by Cursor Bugbot for commit 8311e27. Bugbot is set up for automated code reviews on this repo. Configure here.

Adds a Tool Executions page under Operate > Governance, next to Audit
Logs, covering the dashboard surface and read API shipped in
ArcadeAI/monorepo#2661 and #2662.

The page serves both jobs the feature exists for: a developer debugging
why a tool call failed by reading the exact inputs and outputs, and an
operator reviewing what a project ran for compliance and usage. It
documents the access split those PRs introduced — the history is
readable by anyone with a role on the project, while the recorded inputs
and outputs take project-admin authority, and diagnostics stay readable
either way.

Also cross-links the page from the developer-facing tool error handling
guide, and adds it to the Governance and Operate card grids.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Aug 15, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview Aug 18, 2026 11:45pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant