Skip to content

Archive and channels

Ask for it when you no longer need an agent or a group:

Archive Editor.

Archiving deletes nothing; the channel and its history stay. The agent calls archive with the name of an agent or a group.

What it does to an agent:

  • Its channel moves to an Archive category, where nothing answers.
  • Its schedules are cancelled.
  • It leaves every group it was in. A group left with fewer than two members is archived too.
  • Its name stays reserved, so a new agent or group needs a different name.

What it does to a group: the channel moves to Archive, and the members stay as they are.

There is no unarchive tool. The coordinator in the entry channel cannot be archived. An agent cannot archive itself, so ask another agent to archive it. Deleting an agent’s or a group’s channel in Discord by hand also archives that agent or group.

Put Researcher and Editor in a category for work, with Editor first.

The agent calls channel_arrange with a list of categories, each with the agent or group names that go in it, in order.

  • Agents go under Agents or Agents-<suffix>, and groups under Groups or Groups-<suffix>. The suffix is 1 to 32 characters.
  • A category that does not exist is created.
  • The categories you list come first in the server, in your order. Every other category follows as it was.
  • In a listed category, the channels you list come first in your order, and its other channels follow as they were.
  • An Agents or Groups category left empty is deleted.
  • A wrong entry refuses the whole call, and nothing moves.

agent_list shows every agent and group with their channels and the current categories, so the agent can read the layout first.

channel_read reads messages of a text channel or a thread in the agent server, and changes nothing. An agent uses it when you forward a message and it needs what was said around it.

Field What it is
channel The channel, as <#id> or its id.
around Optional. A message id: read the messages around it instead of the latest.
limit Optional. 1 to 50 messages, 20 by default.

The messages come oldest first, each with its id, time, author, text, and attachment names. Any speaker can use it.

In the research channel, Researcher answers a request with two bullet points and notes that the result was handed to the editor channel.

An agent can hand a request to another agent with message_agent. It takes to, the other agent’s name, and text, a self-contained request of up to 4,000 characters. An agent has one conversation on each surface, its Discord channel and its room in the web app, and the request lands in the target’s conversation on the sender’s surface: its room when sent from a web room, its Discord channel when sent from Discord. It never follows the target onto another surface. An optional conversation picks another: discord, web, or one of the conversation keys agent_get lists.

  1. The call returns at once, so the sender keeps going.
  2. The request appears in that conversation under the sender’s name. The target works there, in its own conversation.
  3. The sender’s conversation shows the exchange as small cards: → To the target with the request’s first line when it is sent, then ← From the target with the answer’s first line, or a card saying no answer came. Each card opens to its whole text: a click in the web app, the Show all button on Discord, which answers only whoever pressed it. No thread is opened. An empty answer shows no card.
  4. The answer comes back to the sender as a new turn, in the conversation the sender wrote from, and the sender tells you what matters.

A chain of agent messages stops at 8 messages without you in between. The agent then tells you what was done and asks whether to continue.

Ask the coordinator for a result that needs two agents, and it can pass work along:

Have Researcher find three sources on this topic, then ask Editor to turn them into a paragraph.

Inside a group, agents use mentions to hand the conversation to each other; message_agent is for conversations outside the group.