Skip to main content

ffwf-tau

The guessable name for Tau, a programmable coding-agent harness with an optional TUI.

pip install ffwf-tau
tau

This distribution contains no code. It depends on the other Tau distributions at the same version, with the extras that make the program complete on its own, so the two commands above install tau and start it.

Why it exists

Tau publishes four distributions, and none of them is called ffwf-tau:

Distribution Imports as What it is
ffwf-tau-llm tau_llm the provider and streaming layer
ffwf-tau-agent-core tau_agent_core the agent loop, tools, sessions, extensions
ffwf-tau-coding-agent tau_coding_agent the tau command and the Textual TUI
ffwf-tau-jmfts tau_jmfts the optional JMFTS session store

pip install ffwf-tau used to fail with could not find a version that satisfies the requirement, which reads as "wrong Python" or "wrong index" and is neither. It also matches the name of a command Tau already installs: the ffwf-tau executable is the prefixed spelling of tau, for scripts that need a name PyPI guarantees. One name now means one thing in both places.

Note the ffwf- prefix throughout. tau, tau-llm, and tau-ai on PyPI are unrelated projects.

What you get, and what you do not

ffwf-tau is the completionist install — everything that works on its own:

It pulls in So that
ffwf-tau-coding-agent[tui] the CLI, the headless modes, and the Textual interface
ffwf-tau-llm[anthropic,google] all three wire protocols, not just openai-completions
ffwf-tau-agent-core[images] read on a screenshot works, bounded to 2000px a side

The provider SDKs and Pillow are extras on their own distributions, and each raises an error naming its extra when it is missing. That is a good failure, and still one the guessable name should not hand you.

It deliberately does not pull in [jmfts]. The JMFTS session store needs a running server, so an install that added it by default would answer a question nobody asked. Install it when you want it:

pip install 'ffwf-tau-coding-agent[tui,jmfts]'

If you want the headless agent without any interface libraries, provider SDKs or native image wheels, install the real distribution rather than this one:

pip install ffwf-tau-coding-agent

Everything else

Documentation: https://ffwfrobotics.github.io/tau/

Repository: https://github.com/jmccardle/tau

MIT © Fight Fire with Fire Robotics, LLC

Metadata

Release files for ffwf-tau 0.10.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for ffwf-tau 0.10.1
File Size Uploaded
ffwf_tau-0.10.1.tar.gz 4.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for ffwf-tau 0.10.1
File Interpreter ABI Platform
ffwf_tau-0.10.1-py3-none-any.whl Python 3 none any Details

Total release size: 8.3 kB

Release files / ffwf_tau-0.10.1.tar.gz

Download URL ffwf_tau-0.10.1.tar.gz
Size 4.6 kB
Tags Source
SHA-256 checksum
How to use checksums
04cbdc6c5aea5ca43fa91e457e06b1c2ca8bddda55c13bce26661b5f9f4c3968
BLAKE2b-256 checksum
How to use checksums
89ee774200918cc85821137a39e0537cd8e1356e3788575265b3ad7e35e2cb3e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.

Transparency log

Release files / ffwf_tau-0.10.1-py3-none-any.whl

Download URL ffwf_tau-0.10.1-py3-none-any.whl
Size 3.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8e66c441b0d9dfcd41395bf44717fc9e05e9b25c5323e6770d303d9048fe6c9e
BLAKE2b-256 checksum
How to use checksums
16f75716138360e2e7a8cbf662cf588c99f9b333df0e6395f4cac9f1057645d5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 9, 2026.

Transparency log

Release history Release notifications | RSS feed

0.11.0

2 release files

0.10.3

2 release files

0.10.2

2 release files

This release

0.10.1 This release

2 release files

0.9.7

2 release files

0.9.6

2 release files

0.9.5

2 release files

0.9.4

2 release files

0.9.3

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page