Hugging Face Tau Integration¶

SuperQode treats Hugging Face Tau as an optional harness, not as the main execution layer. Tau keeps ownership of its provider-neutral agent loop and append-only session, while SuperQode normalizes progress into Harness Protocol events and records it in the existing evidence store.

Install and select¶

uv tool install "superqode[tau]"

In the TUI, run :tau use, or open :connect, select Other harnesses, then select Tau (Hugging Face). The entry remains visible when the extra is missing and shows an installation command appropriate for the environment running SuperQode.

:tau use
:harness switch tau

From the root :connect picker, press H to open Other Harnesses.

Native Tau commands¶

SuperQode manages Tau without requiring Tau's TUI or /login command:

:tau help
:tau login
:tau status
:tau providers
:tau models [provider]
:tau model <provider>/<model>
:tau sessions
:tau logout <provider>
:tau retry

:tau login registers or updates the route in Tau, copies the credential from SuperQode's local auth store, selects the Tau harness, and connects the session. It does not require a separate :connect command when the route is supplied. For unauthenticated local providers such as Ollama, SuperQode stores a harmless local placeholder because Tau requires a non-empty credential value.

For example:

:tau login ollama/qwen3.6:35b-mlx

Then send a message normally. If a Tau request previously failed with Unknown provider: ollama, finish with:

:tau retry

Bare :tau login reuses the active SuperQode route when one already exists:

:connect local ollama/qwen3.6:35b-mlx
:tau login

Ollama is registered through its OpenAI-compatible endpoint at http://localhost:11434/v1, respecting OLLAMA_HOST when it is set. After initial setup, :tau use reconnects Tau's configured default route.

Current safety boundary¶

The maintained tau preset is intentionally read-only. It gives Tau its read tool but withholds write, edit, and bash because those native tools do not yet participate in SuperQode's approval and sandbox policy.

Do not make Tau the default/main layer yet. Keep it as a canary integration until a tool-governance bridge can enforce SuperQode permission decisions before Tau executes a mutation.

Event and session mapping¶

Tau is not pulled from models.dev because that service catalogs models and providers, not agent harnesses. Tau is also not currently listed as an ACP agent. SuperQode therefore discovers it as a pinned optional Python dependency and direct Harness Protocol adapter.

Next adoption gates¶

Before enabling coding mode by default:

1. Wrap Tau tool execution with SuperQode approval and sandbox policy.
2. Add provider/model alias mapping between the two catalogs.
3. Run write/edit/bash conformance tests in an isolated worktree.
4. Track upstream pre-1.0 compatibility and update the current tau-ai>=0.3.3,<0.4 pin deliberately.
5. Consider contributing an ACP server upstream if Tau adopts ACP; do not create a private pseudo-ACP dialect in SuperQode.