Skip to main content
Before every answer in a chat, Blue reads the chat’s Context page, the project’s Project context and any Rules for Blue. Edit them, and Blue’s next answer follows.

​
Chat context

Each group chat with Blue has a Context page: what the chat is for, what’s been decided and who does what. Anyone in the chat can edit it.
Open the chat’s info and tap Chat context. If the chat doesn’t have one yet, tap Start this chat’s context.
How Blue fills it in. Blue writes a first draft from the conversation, and it waits until someone taps Accept or Reject. After that, Blue keeps the page up to date itself. If a chat admin turns off the context switch, Blue’s changes wait as suggestions instead. Ask Blue to remember something. In the chat, say something like “@Blue remember that deliveries come through Gate 2”. Blue adds it to the chat’s Context page. Undo a change. Open History and tap Restore on an earlier version.

​
Project context and the wiki

Each project’s wiki has a Project context page. It appears once a group chat in the project has Blue. Blue suggests entries for it from the project’s chats: things that hold across the whole project, such as site rules, working hours, site access, standards, owners and decisions. A person accepts each suggestion. Accepting it shares that entry with everyone in the project. Answers in the project’s group chats read the Project context alongside the chat’s own page. Where the two differ, the chat’s page wins in that chat.
Open the project details and tap Project wiki.
Project members can edit project pages. Only organisation owners and admins can add organisation pages. Blue doesn’t read archived pages.

​
Rules for Blue

Rules tell Blue how to behave. For example:
  • “Send pricing questions to the project manager. Never quote prices.”
  • “Keep answers short and use bullet points.”
Rules live in a Rules for Blue box at the top of a chat’s Context page and of the project’s Project context page. Chat admins edit a chat’s rules, and project admins edit the project’s rules. Everyone in the chat or project can read them.
Tap Edit in the Rules for Blue box. Rules can be up to 2,000 characters. Earlier versions shows past versions.

​
Project rules and chat rules

Blue follows the project’s rules in every chat in the project, plus each chat’s own rules. Where they differ, the chat’s rules win. A chat’s Context page shows the project’s rules too, so you can see what the chat’s rules would override. Ask Blue across your whole organisation doesn’t use rules.

​
Blue checks your rules before you save

When you save, Blue checks your draft first and shows Checking…. It flags up to 5 things worth a look:
  • Repeated: a rule says the same thing as another.
  • Contradicts: a rule clashes with another one, or with the project’s rules.
  • Sounds like a fact: this belongs on the Context page instead.
  • Rules can’t do this: something rules can’t change.
Choose Keep editing or Save anyway. The check never stops you saving.

​
What rules can’t do

  • Rules can’t let Blue see or share more, change who sees an answer, or skip a person’s confirmation.
  • Rules can’t make Blue invent facts. Put facts on the Context page.
  • Rules can ask for no links. Blue still includes a source when it speaks up unasked, because it only speaks up when it can link one.
  • Blue only follows rules that everyone reading its answer can see. In a chat with someone from outside the project, Blue leaves out the project’s rules.
  • Blue never writes or suggests rules itself.