Skip to main content
Everything px0 could do, it could only do if you already knew it was there. Running a workflow meant knowing a workflow existed and typing its id. px0 brain ask answered from material you had ingested and, by design, never touched connectors - so it could tell you what a post said about caching, and not what was on your calendar. px0 ask is the front door. You ask; px0 works out who should answer.

​
Where a question can go

The route px0 chose is printed above the answer, so a question that went somewhere surprising says so instead of leaving you guessing.
Pin the route yourself when you already know where a question belongs, or when the router keeps getting one kind of question wrong:
--explain prints the routing decision and stops. Nothing runs and nothing is answered.

​
Two limits, on purpose

A question is never permission to act. A workflow with any write tool is confirmed by name before ask will run it - “what does my standup look like” must not post it - and in a non-interactive shell it is refused rather than assumed. Pass --yes to waive that.
The router is only ever shown read-only tools. A router one bad classification away from sending something would undo the whole argument for a front door being safe to ask.

​
Conversations

With no question and a terminal to type into, px0 ask opens a conversation instead of answering once and forgetting.
Two things change once there is a thread. A follow-up is understood in terms of what came before, so “and last week?” - which names no subject and is unroutable on its own - still lands. And a turn that reads as putting px0 right is marked as a correction. Corrections are the reason this exists. What you say when an answer is wrong is the highest-signal thing you will say all day, and it used to be discarded the moment the command exited. At the end of a conversation px0 reads them for standing facts and offers to keep the ones worth keeping:
Nothing is kept without you saying so. --no-remember skips the offer entirely.
The conversation itself is scaffolding. It lives under .state/sessions/ and is pruned after ask.session_days (7 by default). What survives it is what you agreed to remember, which becomes an ordinary versioned file under memory/.

​
Questions you keep asking

Every ask is recorded as a run, like everything else px0 does. When the same question comes round for the third time, px0 says so:
The observation worth surfacing is not that you repeated yourself. It is that you keep doing by hand something that could have been waiting for you.

​
Flags

Memory

What px0 knows about you, which every route can draw on.

Ask your brain

The narrow, brain-only ask. Still there, still means exactly that.