Skip to main content

Teach by chat

The lightest way to teach: just type it. Good for rules, preferences, terminology, and concepts, plus outlines of workflows.

Entering Teach Mode​

  1. Start a new conversation.
  2. In the menu next to the + in the input bar, toggle Teach (or click the Teach chip that appears). A Teach label shows up to the left of the text box.
  3. Start typing to teach it.
The mode locks

While the conversation has no messages yet, you can toggle Teach on/off freely. Once you send the first message, the mode is fixed and can't be changed — to switch, start a new conversation.

📷 Screenshot

Place a screenshot of the "Teach chip + Teach menu item" here (static/img/teach-chip.png).

What to teach this way​

  • Business rules: "When an expense invoice is no more than ¥500, the submission note may be left blank."
  • Personal preferences: "When running a task, merge multiple tool calls into one actions array." "Always save screenshots to D:\shots\ with a timestamped filename."
  • Platform terminology / concepts: "What our back office calls a 'frozen order' means setting the order status to hold — don't ship it, don't refund it."
  • Workflow outlines: describe the steps of an operation in text (if there are many steps or the on-screen targets are tricky to describe, switch to Teach by recording — a demo leaves far less ambiguity than a description).

Correcting or supplementing an existing memory​

If something you taught before is now wrong, or not complete enough, just say so in a Teach-mode conversation:

Step 3 of the expense workflow I taught you is off — now step 3 picks "expense type" first, then enters the amount, not the amount first.

It will: check the memory base index (to find where that memory is), read the original text, and update that entry — rather than creating a duplicate. When old and new conflict, your latest explicit statement wins.

How it organizes what you said​

It doesn't store your wording verbatim — it organizes it into something clear, executable, and reusable:

  • Rules/preferences — organized freely by content, but kept clearly structured.
  • Workflows — organized into "Overview / Initial state / Steps (each with a stage result)" (the same format the recording pipeline produces for an "operation description"), with on-screen targets written unambiguously, e.g. "click the blue 'Submit' button below the 'Password' field" rather than just "click submit".

Tips​

  • Teach one thing at a time — easier to record accurately than dumping everything at once.
  • Not sure it got it right? Ask it to repeat it back, or check the entry in the memory base.
  • A one-off instruction doesn't have to be filed — when it judges there's no reuse value it'll say it won't write it; that's normal.

Next​