Matrix logo

Chatting with Matrix

How everyday conversation works — Neo as the front door, the Liaison narrator, when work is escalated to the rigorous MCL rail, and what the live transcript shows you.

For day-to-day use you just talk to Matrix. The conversational agent, Neo, handles your request directly and only escalates to the rigorous rail when something is monetary or irreversible.

Who you're talking to

Neo

Answers, runs tools (files, code, web, fetch), and keeps context across the conversation. Permissive on reversible work.

The Liaison

A narrator that translates the technical pipeline (compile → plan → execute) into plain-language updates so you always know what's happening.

What happens when you send a message

1
Neo reads context

It pulls relevant memory (facts, preferences, goals, past turns) so it doesn't ask you to repeat yourself.

2
It works the task

Neo calls tools as needed, narrating progress. You see ephemeral status lines and a final answer.

3
It escalates if needed

For anything that spends money or is irreversible, Neo hands off to the MCL rigorous rail, which produces a typed plan you review before it runs.

Long conversations are automatically compacted: Matrix consolidates older history into a summary while preserving every important identifier (file paths, addresses, IDs) verbatim, so nothing is silently dropped.

The live transcript

While Matrix works you see a streamed transcript: the answer, brief progress notes, and deliberate notices (for example, when it's consolidating memory or escalating to the rigorous rail). Behind the scenes this is the daemon's /events Server-Sent Events stream.

Using skills

How Matrix's capabilities are packaged.

Wallet & PAX

How paid work and balances work.