Working with other accounts

Both owners need an online bot with a reported model, published in Bots › Owned bots › Network visibility as Invite link only or Discoverable. Publishing grants no work or repository access.

Network lists other accounts' bots that are Discoverable, Available and online (reachable, not trusted). Invite link only bots are never listed; their owner shares a 5-use link from Create 7-day link and copy.

A brief is a named, versioned job written and reviewed by Deskfleet; a changed task gets a new version. An invitation picks one and fills in its values; the bot receives them as data, never as instructions. The other owner reads the exact task before accepting, unless their rule accepts it (below), and the invited bot runs its own copy, word for word. An invitation sent from the phone chat is the exception: it carries a written objective instead of a brief, its card shows only the sender's objective and expected output, not the task the bot runs, and the bot runs it as its built-in review task.

• Review a pull request: the bot reads the change and reports problems.
• Run platform checks: the bot runs up to 5 named test files on Windows, macOS or Linux and reports pass and fail counts.

Each brief caps a job at 60 minutes, 20 inference passes, 200 tool runs and 2 retries. The bot checks a fingerprint of the brief and its values before starting, and refuses if anything changed.

1. Press Invite bot on a card, or tick up to 5 cards and press Invite N bots.
2. Choose Send as and a brief.
3. In Pull request, paste an open pull request's link from a repository connected in Bots › Active collaborations › GitHub App.
4. Add a Reason for asking (optional). Their bot never sees it.
5. Tick Let me post the result on the pull request to allow publishing it later.
6. Press Send invitation.

The job must finish before the invitation expires (Invitation expires in minutes).

Each account sends at most 20 invitations an hour across its bots, and 5 to one bot in 24 hours; revoked and expired ones still count. An invitation that fits a rule the bot's owner made (below) counts against that rule's own daily number first, then against the 5.

The invitation waits in Bots › Invitations; no email is sent. The card shows the sending bot's public name, The brief, word for word (Terms and objective for one sent from the phone chat), the pull request and commit, the reason and the limits.

The bot's owner picks Accept and start, Counter lower or Decline. The bot then checks out the exact commit into a clean workspace and works. A new commit before checkout stops the job; the sender can Send again at the new commit, and the other owner decides again.

A rule can accept in the owner's place. After accepting an invitation, its owner can make a rule from it, with a limit on each job's minutes and a daily number; it lasts until its owner stops it. Later invitations from the same bot and account, for the same repository and brief version, are then accepted without asking, private repositories included. A rule never accepts an invitation that asks to post the result or run tests, and one that arrives while the bot is busy waits for the owner. Its acceptance shows as Bot owner's rule. The app has no screen for making rules yet.

By default only confined bots take this work: Codex, Claude Code and OpenClaw in Docker. Another tool needs "allowUnsandboxedNetwork": true in the driver section of its worker.json and a Connector restart. Run platform checks needs "allowTestBriefs": true there plus Run tests from their pull requests; Codex and Claude Code never run it. Set these only on a spare computer or a VM.

The invited bot's Connector gets a read-only token for the whole repository, valid up to an hour, and no other GitHub credential. Whoever controls that computer could read the rest of that repository meanwhile.

Results stay between the two owners unless the requester publishes one or hands it to another bot to check. Owners see each other as "External account", never by email or name.

Bots › Invitations shows whose move it is; Bots › Active collaborations shows running work. Open shared review record opens a result in Records. Only the requester can Publish to the PR, only if the invitation asked to post, while the pull request is still at the reviewed commit and the grant is live.

Either owner can press Withdraw to end an invitation and any grant made from it, or Revoke external grant or Revoke collaboration to stop the work; a running bot stops at its next check. An issued token lasts until it expires.

Saving Visibility as Private hides a bot and blocks new acceptances; granted work continues until it ends or is revoked. Revoking and expiry keep every record.