Skip to content
Fito

TUI command reference

Fito adds twenty-three slash commands to a pi session. This page is the list: what each one does, what you type after it, and where the full instructions are.

It teaches none of them. Every row links to the page that does.

How to read this page

Section titled “How to read this page”

The commands are pi slash commands. You type them in a pi session, in any folder — not in your shell. If a command is not offered by autocomplete, Fito is not loaded; see Troubleshoot installation.

Every Fito command begins with fito-. The prefix is not decoration: pi ships its own /login and /logout, and a command whose name collides with a builtin is dropped from autocomplete without a warning.

Arguments are written in the usual notation:

Notation Meaning
<name> A value you supply
[part] Optional
a|b Choose one
... May repeat

Session

Section titled “Session”
Command What it does Full page
/fito-login Opens your browser, signs you in, and writes the tokens to ~/.fito/credentials Log in from the terminal
/fito-logout Revokes the refresh token on the server and deletes the stored credentials Log in from the terminal
/fito-auth-refresh Exchanges the stored refresh token for a fresh pair Log in from the terminal

Working a case

Section titled “Working a case”
Command What it does Full page
/fito-case-open Forks the case to your GitHub, clones it, cuts your working branch, and briefs you on the situation and the task Open and work a case
/fito-tutor Asks the Fito tutor about the case you have open. The tutor reads the case and the components it references, never the solution Ask the tutor
/fito-evaluate Scores your local checkout against the case rubric. A dry run: nothing is pushed and nothing is recorded How a case is scored
/fito-submit Pushes your committed work, opens the pull request, evaluates it, and records the result on your profile Submit and read your result

Authoring knowledge

Section titled “Authoring knowledge”
Command What it does Full page
/fito-create-or-update-technology Admits a technology and one of its major lines into the knowledge vocabulary Provision a technology
/fito-create-or-update-competence Records a competence a technology demands, formed from live knowledge components, or edits one’s name and description Author a competence
/fito-delete-competence Deletes a competence and every sub-competence beneath it, after showing you what would go and asking Author a competence
/fito-fetch-urls-content Reads a file of URLs, fetches each page or YouTube transcript, cleans it, and saves it as raw markdown Fetch documentation from a URL
/fito-identify-domain-concepts Extracts candidate concepts from an ingested source Identify knowledge components
/fito-identify-execution-facts Extracts candidate execution facts from an ingested source Identify knowledge components
/fito-identify-usage-scenarios Extracts candidate usage scenarios from an ingested source Identify knowledge components
/fito-generate-domain-concepts Writes full concept content for candidates the identify step found Generate and push components
/fito-generate-execution-facts Writes full execution-fact content for candidates the identify step found Generate and push components
/fito-generate-usage-scenarios Writes full usage-scenario content for candidates the identify step found Generate and push components
/fito-push-knowledge Stores generated component files in Fito, one at a time, stopping on a similar or duplicate component for you to choose Generate and push components

Authoring a case

Section titled “Authoring a case”
Command What it does Full page
/fito-case-design Scopes a goal and its technologies into a case proposal, grounded in live knowledge components Design a case
/fito-case-generate Turns the proposal into the .case/ contract in a working directory, and validates it Generate the .case/ folder
/fito-case-plan-source Writes the spec and the ordered plan for the source work you then do outside Fito Plan the case source
/fito-publish-case Pushes the case to GitHub and registers it with Fito. One flow serves a first publish and a new version Publish a case
/fito-case-edit Puts a published case back on your disk in authoring shape, ready for an update Correct or retire a published case

Arguments

Section titled “Arguments”

Three commands take none:

/fito-login
/fito-logout
/fito-auth-refresh

The rest take these. A case id is the case’s UUID — the <id> from its /cases/<id> address.

/fito-case-open <case-id>
/fito-tutor [<case-id>] [question]
/fito-evaluate <case-id>
/fito-submit <case-id>
/fito-create-or-update-technology --technology <slug>@<version> [--source <path>] [--fetch] [--urls <file>] [--docs <path>] [--output <path>]
/fito-create-or-update-competence --technology <slug>@<version> [--competence <id>] [--output <path>]
/fito-delete-competence [<competence-id>] [--technology <slug>]
/fito-fetch-urls-content <URL list file path>
/fito-identify-domain-concepts <tool-name> --technology-version <slug> [--source <path>] [--technology <slug>] [--description "<text>"] [--fetch] [--urls <file>] [--docs <path>] [--output <path>]
/fito-identify-execution-facts <tool-name> --technology-version <slug> [--source <path>] [--technology <slug>] [--description "<text>"] [--fetch] [--urls <file>] [--docs <path>] [--output <path>]
/fito-identify-usage-scenarios <tool-name> --technology-version <slug> [--source <path>] [--technology <slug>] [--description "<text>"] [--fetch] [--urls <file>] [--docs <path>] [--output <path>]
/fito-generate-domain-concepts <tool-name> --technology-version <slug>[,<slug>...] [--technology <slug>] [--version <ver>] [--concepts <path>] [--output <path>] [--mode one|batch|all] [--select <ids-or-names-or-ranges>] [--audience beginner|intermediate|advanced] [--language <lang>] [--identify] [--source <path>] [--fetch] [--urls <file>] [--docs <path>]
/fito-generate-execution-facts <tool-name> --technology-version <slug>[,<slug>...] [--technology <slug>] [--version <ver>] [--facts <path>] [--output <path>] [--mode one|batch|all] [--select <ids-or-fragments-or-ranges>] [--audience beginner|intermediate|advanced] [--language <lang>] [--identify] [--source <path>] [--fetch] [--urls <file>] [--docs <path>]
/fito-generate-usage-scenarios <tool-name> --technology-version <slug>[,<slug>...] [--technology <slug>] [--version <ver>] [--scenarios <path>] [--output <path>] [--mode one|batch|all] [--select <ids-or-titles-or-ranges>] [--audience beginner|intermediate|advanced] [--language <lang>] [--identify] [--source <path>] [--fetch] [--urls <file>] [--docs <path>]
/fito-push-knowledge [folder-or-files]
/fito-case-design "<goal>" --technology <slug>@<version> [--technology <slug>@<version> ...] [--source <path>] [--output <path>]
/fito-case-generate [<proposal-path>] [--dir <path>]
/fito-case-plan-source [<case-dir>] [--scenario reuse|greenfield] [--proposal <path>]
/fito-publish-case [<case-dir>] [--repo <owner>/<name>] [--case-id <uuid>]
/fito-case-edit <case-id> [--dir <target>]

Each flag is described on the command’s own page, linked in the tables above.

Which commands need you logged in

Section titled “Which commands need you logged in”

Seven write to Fito on your behalf, so seven need a login:

Command Why
/fito-case-open Records the enrolment against your account
/fito-submit Records the submission and the result on your profile
/fito-create-or-update-technology Writes the technology and its major line
/fito-create-or-update-competence Writes the competence, or edits its name and description
/fito-delete-competence Deletes the competence and everything beneath it
/fito-push-knowledge Writes the components
/fito-publish-case Registers and publishes the case

/fito-logout and /fito-auth-refresh act on credentials you already have.

Every other command runs without one. Each either stays on your disk — /fito-evaluate, /fito-case-generate, /fito-case-plan-source, /fito-fetch-urls-content — or reads the Fito server over calls that are public: /fito-tutor, /fito-case-design, /fito-case-edit and the six identify and generate commands.

Which commands need pi-subagents

Section titled “Which commands need pi-subagents”

Every command runs inside a pi session, so every command runs on the model provider you configured. Fito holds no LLM key of its own.

Eleven go further and hand their work to a worker persona. Those need the pi-subagents package installed, and say Unknown tool: subagent without it:

Command The work handed over
/fito-tutor Answering your question
/fito-evaluate Judging the rubric
/fito-submit Judging the rubric
/fito-create-or-update-technology Drafting the two descriptions
/fito-identify-domain-concepts Reading the source
/fito-identify-execution-facts Reading the source
/fito-identify-usage-scenarios Reading the source
/fito-generate-domain-concepts Writing the content
/fito-generate-execution-facts Writing the content
/fito-generate-usage-scenarios Writing the content
/fito-case-plan-source Writing the spec and the plan

/fito-fetch-urls-content needs one thing no other command does: a python3 that can create a virtual environment. The fetch installs its packages there rather than into your system.

What’s next

Section titled “What’s next”