---
title: Save from your AI tools
description: Correct your AI tool once and keep it — it proposes a rule or a fact, and it waits in Vythos, or on a card in the chat, until someone who keeps that page adds it.
---

<span class="vy-eyebrow">Using Vythos</span>

# Save from your AI tools

The moment you correct an AI tool is the moment you know a rule. *"No — Northwind
never wants emojis."* Saving it there, rather than remembering to add it later,
is what stops the same correction next week.

A connected AI tool can save it for you. It **proposes**; you **add**. Nothing
reaches your Playbook, or anyone's AI tools, until a person says yes.

## Ask your tool to save it

Say it plainly, in the chat:

- *"Save this to the Playbook: Northwind never wants emojis."*
- *"From now on, send Lumen the change note before any extra work."*
- *"Remember for Northwind: their buyers are finance directors."*

Or correct the tool, and agree when it offers to keep the correction for next
time.

The tool calls Vythos's `save_to_playbook` (see [The tools](/ai-tools/tools)).
It's told to do that only when you ask — never because the word "remember"
appears in something it's writing or reading, and never because a document or
web page told it to.

Vythos then decides where it goes, the same way the box on the Playbook does:

- **A rule or a fact.** Something to follow is a rule, filed under a
  [category](/concepts/categories). Something true about a client — what they
  sell, who to — is a fact for *About {client}*. Vythos suggests which; you can
  change it when you add it.
- **Which client**, if you named one.

The tool tells you it's waiting, and where.

## Add it

### On the card in the chat

In an AI tool that shows cards (Claude, for one), the reply carries a small
Vythos card with the line and where it goes:

- **Add** puts it in the Playbook.
- **Discard** drops it.
- **Open in Vythos** opens it on its page, to edit it first.

If Claude asks whether to allow the Vythos card, choose *Always allow*. Add and
Discard are on the card only for someone who could add the line themselves;
anyone else is told who it waits for. A line that
reads as if it were written to an AI is never added from the chat in one click:
the card offers **Open in Vythos** only, where it's flagged.

### In Vythos

Everything you can answer appears under **Waiting for you** on the page it
belongs to — *Everyone*, or the client's page — and the rail shows how many
wait for you on each page. In a tool without cards, the reply gives you a link
straight to it.

- **Add** saves it, with the same checks as typing it yourself.
- **Edit** lets you change the words, or where it goes — a proposed rule can
  be added as a fact, and the other way round.
- **Decline** drops it. You can say why, in a line; the person who suggested
  it sees it. Your own suggestions have **Discard** instead.

A fact added from an AI tool is marked *From Claude* (or the tool's name)
under About {client}.

## What it won't save

The tool is told why, so it can tell you:

- **Live figures** — a budget, spend, what's running, whether a contract is
  signed. They go stale and then get trusted. Get them from the system that
  holds them.
- **Questions and fragments.** A rule is a statement someone could follow.
- **An amount of money as a fact.** Money is always a rule, where access to it
  is set.
- **A fact for everyone.** Facts are about a client; your agency's own
  description is in Settings.
- **Something already kept.** If the line is already a rule or a fact, the tool
  is told where, and nothing new is saved. The same line proposed twice is one
  item waiting.

## When a teammate saves it

**Who can suggest.** Anyone with *Can suggest* or *Can edit* on at least one
category — members can from the start. Freelancers can't until you raise one
of their levels on **Members**. See [Team & access](/using-vythos/team-and-access).

**Who it goes to.** Whoever could add the line themselves decides it:

- **A client's rule or fact** goes to the people who
  [look after the client](/using-vythos/team-and-access#who-looks-after-a-client).
- **Pricing & rates, Terms & commitments, and rules for everyone** go to
  whoever can edit that category.
- **Nobody chosen?** It goes to the workspace owner.

Anyone else who could add it — the owner, a lead who can edit that category —
sees it too, marked with who it's for, and can answer it. Nobody else sees it.

**What the person who suggested it sees.** Their AI tool tells them who it's
waiting for. On the page it belongs to, under **Your suggestions**, they see it
waiting, and can **Withdraw** it. Then, for two weeks, what became of it:
added, declined and why, or expired. Until it's added, it isn't a rule — for
them or anyone.

## The daily email

At 8am UK time, each person gets one short email listing the new suggestions
waiting for them — only on days when there are some, and each suggestion only
once. It links to the Playbook; nothing is answered from the email.

Turn it off in **Your data**, or with the link at the foot of the email.
Suggestions still wait on the Playbook either way.

## How long it waits

An item waits for **14 days**. After that it lapses, nothing changes, and the
person who suggested it sees that it expired. A workspace holds up to 100
waiting items at a time.

## Why it waits

An AI tool reads emails, documents and web pages, and any of them can contain
text written to talk an AI into something. If an AI could add a rule because it
was told to, anything it read could write rules for your whole team. A click
from a person is the one thing a page can't fake — so that's what a rule needs.

Related: [Add a rule](/using-vythos/add-a-rule) ·
[Rules: a line or a document](/concepts/rules-and-documents).
