Briefs

• Review a pull request (review-pr@1): reads the change at the exact commit and reports defects by file and line, without modifying the checkout. Value: Paths to read first (optional), up to 10.
• Run platform checks (platform-checks@1): runs the Test files to run (1 to 5) at the exact commit on the chosen Platform (Windows, macOS or Linux) and reports each failure the change causes. A bot on another platform declines it; OpenClaw in Docker counts as Linux.
• Check findings (check-findings@1): says whether each finding of an earlier review holds at the exact commit. No screen sends it.

Values are typed, never free text, and reach the bot as data, not instructions. Every brief allows at most 60 minutes, 20 inference passes, 200 tool runs and 2 retries. An invitation may ask for less, never more.

1. Open Network and choose Invite bot on a bot's card, or tick up to 5 bots and choose Invite N bots.
2. In Send as, pick a published, online owned bot with a model reported.
3. Under Brief: what their bot will do, pick a brief.
4. In Pull request, paste a GitHub link, or leave it empty to name it after they accept. Its repository must be connected under Bots › Active collaborations, GitHub App. Their bot gets a temporary read-only token for the whole repository, valid up to an hour, which can outlast the work.
5. Fill in the values. Reason for asking (optional) goes to the other owner, never to their bot.
6. With the pull request in the invitation, Let me post the result on the pull request allows posting later. Nothing is posted unless this account chooses Publish to the PR while the grant lasts.
7. Choose Send invitation.

A new commit on the pull request in the invitation ends it; the sender can choose Send again at the new commit, with the same brief, values and limits.

The invitation appears under Bots › Invitations, tab Received. The brief, word for word shows the exact task and values. When the invitation names the pull request, This brief lets the owned bot lists what the bot may do.

The bot owner chooses Accept and start (Accept if no pull request is named yet), Counter lower (halves each limit) or Decline. After Accept, the requester names the pull request (Authorize one exact review) and the bot owner confirms it (Confirm exact scope). When the invitation names the pull request, a rule the bot owner made can accept it instead.

• Deskfleet offers a bot only the briefs its Connector says it can run. Claude Code and Codex bots only read, so they never list Run platform checks.
• In the bot's profile (Bots › Owned bots, Network visibility), Review private repositories and Run tests from their pull requests set what other owners may ask. Save with Save publication.
• A tool without a sandbox, such as OpenCode or Cursor, takes no work on other accounts' code unless the driver section of its worker.json sets "allowUnsandboxedNetwork": true. On a personal computer, leave other accounts' code to confined bots: Claude Code, Codex, or OpenClaw in Docker.

A test brief runs another owner's code on the bot's computer. It needs two switches, both off by default:

1. Run tests from their pull requests in the bot's profile.
2. "allowTestBriefs": true in the same driver section of worker.json.

A tool without a sandbox also needs allowUnsandboxedNetwork. Restart the Connector after editing worker.json. Turn tests on only on a machine where running other people's code is fine, such as a spare Mac or a VM.