Wait for Capy agents to finish
capy_waitWait for one or more Capy threads to finish and retrieve their results. Returns early if a thread is blocked on human input, or reports progress after a timeout.
Instructions
Block until one or more Capy threads finish, then report what happened. This is what turns a fleet of background agents into something you can use inside a single conversation: delegate several pieces of work, then wait for all of them here.
The Capy API has no streaming or push notifications, so this polls with backoff. It returns early, without an error, if a thread becomes blocked on a human (an auth or permission gate), so you never sit waiting on something that cannot progress.
If the timeout is reached the result says so and the threads keep running on Capy's side: just call this tool again with the same ids to keep waiting.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| wait_for | No | Return when "all" threads finish, or as soon as "any" one of them does. Defaults to "all". | |
| thread_ids | Yes | One or more thread ids to wait on. | |
| timeout_seconds | No | How long to wait before giving up and reporting progress so far. Defaults to 240. Keep this below your MCP client's own tool timeout. |