Skip to content
Fito

Ask the tutor

When you get stuck inside a case, ask the tutor:

/fito-tutor how should I approach this?

It answers about the case you have open and the knowledge that case references, and about nothing else. This page is about working with that boundary rather than against it.

Before you begin

Section titled “Before you begin”
  • The case is open. The tutor reads your checkout at ~/.fito/cases/<case-id>/; if it is missing, the session points you at /fito-case-open and stops.
  • An LLM provider is configured in pi. The tutor runs on your subscription, not on Fito’s — the server holds no LLM key.

Ask a question

Section titled “Ask a question”
/fito-tutor [<case-id>] [question]

You rarely need to name the case. The command takes the first of these that settles it:

  1. a case id given as the first argument
  2. the case opened earlier in this conversation
  3. the checkout you are standing in, when your working directory is inside ~/.fito/cases/<id>/
  4. the single open checkout, when ~/.fito/cases/ holds exactly one

When none of them settles it, the tutor lists what is open — each case named by its title and type, never by a bare id — and asks which you mean. It never guesses, because a confident answer about the wrong case looks exactly like a right one.

Three things can come back

Section titled “Three things can come back”

An answer. It keeps the knowledge component ids and the .case/ files it drew on, so you can go and read the same sources.

A hand-back. Your question sits outside the case’s purpose — a general language question, or something about your own tooling. The tutor says so and hands it back; put it to your own session instead and carry on. The tutor thread stays where it was.

A refusal. Three things are never given: the exemplar solution, the quiz answer key, and the rubric’s scoring key.

Why the refusal is structural

Section titled “Why the refusal is structural”

That refusal is not politeness, and it is not a rule the tutor is asked to keep.

The tutor persona holds no bash tool and no filesystem tool. The only way it reads anything is a fetch that serves documents by an enumerated key, and the solution, the rubric and the quiz have no key in that set. There is no phrasing that reaches them, because there is no request shape that names them.

This matters when you are stuck. Asking harder will not work, and it is not worth your time. Ask a different question instead:

  • “Which knowledge component is this criterion about?” — in scope.
  • “What does this execution fact actually mean at runtime?” — in scope.
  • “What is the situation document telling me that I might be skipping?” — in scope.
  • “Show me the solution” — refused, structurally.

It remembers the conversation

Section titled “It remembers the conversation”

The first question opens a thread, and every later /fito-tutor goes back to the same worker, which still holds everything said so far. Follow-ups can be as short as you would make them with a person.

The thread lives as long as this pi session does. Close the terminal and the next /fito-tutor starts a fresh one — and the session tells you so, rather than letting you work it out from a tutor that has forgotten where you were.

What’s next

Section titled “What’s next”