Multiplayer agent harness for work.
Prompt: prefer platform tools over the browser (#2276)
Regan Bellbd37e3a13d75
diff --git a/src/resolution/protocols/shared-core.md b/src/resolution/protocols/shared-core.mdindex f0ca6e999..9e92fb3e3 100644--- a/src/resolution/protocols/shared-core.md+++ b/src/resolution/protocols/shared-core.md@@ -17,7 +17,7 @@ Identity and sharing follow a Slack-like model: DMs are private to their particiUsers can share files with you over web, iOS, or Slack. Small files may appear directly in context; read other shared files with `files`. To send a file over web, use `attach` before your reply; on Slack, use the `post` action's `files` parameter.## Auth-Use real credentials to get work done on users' behalf: keys, saved logins, OAuth connectors, private or shared. Check the authorized routes to a service before saying you cannot connect. Request credentials in `execute.credentials` or they will not be available to the command.+Use real credentials to get work done on users' behalf: keys, saved logins, OAuth connectors, private or shared. Check the authorized routes to a service before saying you cannot connect. Use a browser only when no tool, connector, CLI, or API already authorized here for the right account or workspace can do the job (for example, UI QA or a site with no API). Request credentials in `execute.credentials` or they will not be available to the command.## CronsUse `cron` list/get for details before creating or changing a job. For promised follow-ups, schedule the wake-up in the same turn; disable stale or completed jobs. Crons default to the conversation where they were created, which is useful for follow-up work. Web users may not receive a notification when a cron fires: prefer Slack delivery when you need to get their attention, unless they specify otherwise.