How learning works
There’s no training mode and no settings page. Learning happens as a natural by-product of working together:You work naturally
Ask for things, correct what comes back, explain your preferences —
exactly as you would with a new colleague.
Your assistant reviews its own work
After it finishes a piece of work, your assistant looks back over what
happened and asks itself: is anything here worth keeping for next
time? A rule you corrected, a workflow that succeeded, a pitfall it hit
— those get saved. Routine work saves nothing, and that’s by design: a
small, sharp library beats a big noisy one.
What it learns: playbooks and skills
Learned material lands in two libraries, both visible in the Console:Guidance — the playbooks
How you want things done: rules, preferences, step-by-step procedures,
and pitfalls to avoid. “Exclude internal transfers when computing
monthly spend” lives here.
Functions — the skills
What your assistant can do again: concrete, reusable workflows it
built while working for you. The corrected monthly-spend pipeline itself
lives here.
A third library, Knowledge, holds facts —
documents you’ve shared, things that are true about your business.
Guidance is how-to; Knowledge is what-is. Your assistant also quietly
keeps notes on the people you both deal with — their details and
preferences — in Contacts.
Seeing it happen
Learning isn’t a black box. The Console shows you all of it:- The Actions pane shows your assistant’s work live, step by step — including the moment it checks its libraries (“Searching for relevant guidance”) and the moment it saves something new (“Storing reusable skills”).
- The Guidance and Functions panes let you browse everything it has learned, as readable documents and inspectable skills.
What’s in this section
Watching it work
The Actions pane — every request, every step, live.
Guidance & Functions
Browsing the playbooks and skills your assistant has picked up.
Knowledge
The durable facts and rules its answers rest on.
Teaching your assistant
Corrections, walkthroughs, documents — and how to make them stick.
Building on or extending the open-source runtime? The
Developers sub-section documents how
all of this is implemented in
unifyai/unify — the dual library,
the two-phase actor loop, StorageCheck, and the knowledge and memory
subsystems.