Skip to content

Calling a hero by name

A hero goes by its own name. In a mission that has added Kit, type @kit and your question in the chat, and Kit answers in the chat. Cora can also call a hero in herself when what it is good at fits the job (D0857).

A mission must add a hero before anyone in it can call it in. A mission admin opens Mission details, the Tools tab, and under Heroes helping here presses Add a hero. Adding needs no approval from the hero’s own mission (D0719). The hero must also be open to your mission (see who can call a hero).

  1. In the mission’s chat, type @. The list shows the people in the mission, then the heroes added to it that are on.
  2. Pick the hero, or type its handle yourself, for example @kit, and write your question in the same message.
  3. Before you send, a line under the message box says who will see your question:
    • for a hero made from a mission: “Kit is a hero from the Page checks mission. Its members can see your question and the answer.”;
    • for a hero made on the Heroes page: “Scout is a hero with its own training room. Its admins can see your question and the answer.”
  4. Send the message.

A message that names heroes and does not tag @Cora goes straight to each hero named, with your message as the request. Cora does not run for it, so it is faster and cheaper. A message can call in up to five heroes. A message that also tags @Cora goes to Cora, and she decides whether to call the hero in (D0781).

Cora has a tool for calling in a hero, call_hero. She sees each hero added to the mission that is on, with its name, what it is good at and what you wrote under When should Cora call it in?, and calls one in when it fits the work. You can also ask her: “Ask Kit to check this page.”

Cora waits up to 30 seconds for the answer. If the hero has not finished by then, she says it has been called in and carries on with other work. When the answer arrives she is started again to use it.

The hero’s answer comes back into your mission’s chat as a Called in a hero card. The top of the card names the hero that answered: its mini hero, its name and the name on its card. One line says the result and how long it took, for example “Done in 2 minutes”. What Kit did opens your question, the answer, and why it stopped if it did not finish.

When you asked the hero yourself, the card is the hero’s reply to your message. When Cora called it in, she uses the answer in her own work.

  • A summary by default. You get back a summary of at most 4,000 characters. The hero’s admins can choose a full answer instead, up to 20,000 characters.
  • Never its files or chat. The hero sees only your request, never your mission’s documents, connections or chat, and you get only its answer. Whatever it writes stays in its own mission. More on what a hero can do for a caller is in the mission chat.
  • Information, not instructions. A hero’s answer reaches Cora as information, the same as a web page or a file.

If a hero you named cannot start, a short line under your message says why, and nothing is spent on it. For example “@kit could not start: a message can call in at most five heroes.” The reasons are:

  • it is not added to this mission, or it is not open to this mission;
  • it is this mission’s own hero;
  • the message names more than five heroes;
  • the organisation has reached its spend cap;
  • this mission has reached its daily limit for that hero. The limit starts again at midnight in the organisation’s time zone.

Any other hero you named still starts. A handle of a hero that is switched off is treated as plain text: nothing starts, no line says why, and the message goes to Cora, the same as for a handle no hero has (D0796).

The @handle is made from the hero’s name: lower-case, with spaces turned into hyphens, so “Page Checker” is called in with @page-checker. Renaming the hero changes its @handle; messages already sent keep the words they had (D0856).

Two heroes in one organisation cannot have the same @handle, so a name that would give another hero’s @handle is refused: “Another hero in your organisation goes by @kit. Choose another name.”

A hero’s AI work counts toward your organisation’s AI usage like any other work. Each call is tagged to the mission that called. The hero’s admins can set a daily cap for the missions that call it, and the organisation’s spend cap still applies to every call. See hero calls for the details.

Callers and spending. Every member of the hero mission sees which missions have called the hero, and whether each one uses the default daily cap, has its own cap, or is stopped. Only the mission’s admins see what each mission spent today and this month, the caps themselves, and what each incoming task and run cost. They see these as a share of the organisation’s AI usage for the month (or for the whole free trial), never in dollars. Admins set the caps as a percent: 0, which stops the calls, or 0.01 to 100 with no more than two decimals. A cap is kept exactly as typed, and becomes an amount only when a call is checked against it, as that share of the organisation’s AI usage at the time. A percent above 0 but under 0.01, or with more decimals, is refused rather than saved or rounded.

Called in a hero card. The card on the calling mission’s timeline shows the question, the answer and how long it took. It shows no cost.

These are on the hero’s page, under What it has done (D0868, D0869).

  • Calls go at most two missions deep, and the same mission never twice in one chain.
  • Cora calls in at most five heroes in one step.
  • A call has 15 minutes by default and 60 minutes at most.
  • Your private chat with Cora cannot call in a hero. Only the mission’s chat can.