docs: document tool executions in the Operate area - #1129
Open
evantahler wants to merge 2 commits into
Open
Conversation
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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 modified.
Overview
Adds Tool Executions documentation under Operate → Governance for the dashboard and read API shipped in the monorepo.
The new page explains how to debug failed runs (filters, attempts, admin-only input/output toggles) and review project usage for compliance, including the member vs project-admin visibility split, three GET endpoints, and retention defaults.
Navigation and copy are wired through Governance and Operate card grids,
_meta, updated descriptions, a short section on the tool error-handling guide pointing to Tool executions, and anllms.txtindex entry.Reviewed by Cursor Bugbot for commit 5babf63. Bugbot is set up for automated code reviews on this repo. Configure here.