Skip to content

docs: update for 0 changes (2026-07-07) #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
doc-writer-bot wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: update for 0 changes (2026-07-07) #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions agents/app-triggers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,14 @@ Runs are asynchronous: `run()` returns right away and you poll `getAgentContent`
| `getRunningInstancesOfAgent(agentId?)` | List currently live runs. |
| `getAgentContent(chatThreadId, n?)` | Read the last `n` messages of a run. |

## Approving permission requests

An agent an app started can reach a tool set to **Ask** (see [Tool Permissions](/agents/tool-permissions)) — for example a write or delete operation. On an app-triggered run there's no person in chat to approve it, so the run pauses with a pending permission request instead of prompting.

The app that started the run can read those pending requests and approve or deny them, keeping an unattended run moving. As with other run management, an app can only respond to permission requests from runs it started.

<!-- DOCS-BOT: please review — the exact agents-client method names for listing and responding to permission requests aren't confirmed in the source. Add them to the methods table above (alongside `stopAgent`) once known. -->

## Limits

To prevent runaway costs, an app may have a limited number of live agent runs at once; further `run()` calls are rejected until some finish. An app can only manage the runs it started. Manual and scheduled runs aren't subject to this per-app cap.
Expand Down