Skip to main content
A spawned thread in #billing: computer posts a message that mentions Sam, the task, a link to the brief and a link back to the parent thread, and the new session replies under it
When a message to the session contains a Slack message permalink, the gateway attaches the linked thread: its first message, the linked reply and the latest replies. The model receives it marked as data from Slack, not as instructions.
  • At most 3 links per message are read; size limits are in Limits and defaults.
  • The link must be in the same Slack workspace, and @computer must be a member of the conversation it points to.
  • If reading takes more than 10 seconds, the message is delivered with a note that reading took too long.
  • Messages forwarded into the message (up to 3) are attached with no access check.

Access check

A linked thread is attached only if all of these can see the linked conversation:
  1. The person who posted the link.
  2. The session’s owner.
  3. Everyone in the session’s conversation, when it is not the linked one.
The check also refuses when the session’s conversation is shared with another organization, or when a member list it has to read has more than 5,000 members. On a refusal the model gets a note with the reason in place of the content.

Reading and posting tools

Gateway-and-host deployment only. Parameters: Agent tools. post_thread:
  • replies in the thread, never at the channel’s top level;
  • neutralizes @channel, @here, @everyone and user-group mentions;
  • appends a line: “Posted for @owner from this thread.” with a link back.
A reply by computer in another thread in #web, ending with the line Posted for @Sam from this thread

Spawned threads

spawn_thread starts a new session, in a new thread, that runs in parallel. Gateway-and-host deployment only. Parameters: Agent tools.
  • 8 spawns per runner.
  • The parent is not told when the child finishes. The child reports in the brief and in its own thread; the parent can read that thread with read_thread.
  • Steer or stop the child in its own thread. Stopping the parent does not stop it.