TEAA 0.5 alpha — free release

TEAA 0.5 alpha — free release

TEAA (ToolsEnabled Agent Architecture) gives the agent you already use (Claude Code, Codex or another MCP agent app)
a team, hands and a memory: Fleet, ToolsEngine and Knowledge through one local MCP connection. TEAA + FRA + Hub adds
FRA and Hub, so the agents on the computers you enroll work together as one team.

This is an alpha. Interfaces, behavior and packaging can change between releases.

What's in this release

File	What it is	Platforms
teaa-0.5.0-alpha.6-linux-x64.tar.gz, teaa-0.5.0-alpha.6-windows-x64.zip	TEAA 0.5.0-alpha.6: Fleet, ToolsEngine and Knowledge in one local MCP connection. Free; no ToolsEnabled account needed.	Linux x64, native Windows x64 (no WSL)
teaa-extended-0.5.0-alpha.10-linux-x64.tar.gz, teaa-extended-0.5.0-alpha.10-windows-x64.zip	TEAA + FRA + Hub 0.5.0-alpha.10: everything in TEAA, plus FRA (connects the computers you enroll) and Hub (the agents on those computers work as one team). Use it with a ToolsEnabled account, which is free with sign-up for up to 8 computers, or with your own self-hosted server.	Linux x64, native Windows x64 (no WSL)
teaa-hub-server-selfhosted-linux-x64.tar.gz	Self-hosted server: the account service and relay for TEAA + FRA + Hub, for running on your own Linux server. See SELF-HOSTING.md.	Ubuntu 24.04 with systemd
INSTALL.md, SELF-HOSTING.md, SHA256SUMS	Install guide for all three, the self-hosting guide, and checksums for every file.	—

Verify every download against SHA256SUMS before installing (INSTALL.md shows how on each platform).

Components

Component	Version	Public repository, and the upstream source commit it was built from
TEAA	0.5.0-alpha.6	ToolsEnabled/teaa (source 03b99ed)
TEAA + FRA + Hub	0.5.0-alpha.10	ToolsEnabled/teaa-extended (source bdc8d1a)
Fleet	5.0.0-alpha.13	ToolsEnabled/fleet (source 2c37a8a)
ToolsEngine	0.2.0-alpha.4	ToolsEnabled/toolsengine (source 234c472)
Knowledge	1.2.0	ToolsEnabled/knowledge

TEAA, TEAA + FRA + Hub, Fleet, ToolsEngine and Knowledge are open source under the MIT License. The self-hosted
server package carries its own license files; read them inside the package.

Requirements

• TEAA and TEAA + FRA + Hub: Node.js 22.19 or newer. Python 3.11 or newer and Git for Knowledge.
• Fleet workers: a supported agent CLI (for example Claude Code or Codex) with its own sign-in. Setup does not start a worker.
• Self-hosted server: Ubuntu 24.04 with systemd and root access, Node.js 22.23.4 or newer at /usr/bin/node, plus a domain, TLS and an SMTP mailbox for sign-in codes. See SELF-HOSTING.md.

New in TEAA 0.5.0-alpha.6 and TEAA + FRA + Hub 0.5.0-alpha.10 (2026-10-30)

• Python does not have to be on PATH. Setup now uses the Python you set in knowledge.command instead of searching PATH and failing. This mostly affects Windows, where the python.org installer leaves Python off PATH by default. See "Using a Python that is not on PATH" in INSTALL.md.
• Upgrade: stop a running Hub with teaa hub stop, install the new archive into the same prefix, and run teaa setup again with the same options. Fleet state, enrollment, settings and your configured Python are kept.

Earlier in TEAA + FRA + Hub 0.5.0-alpha.9 (2026-10-30)

• Hub on Linux login sessions. The Hub's FRA gateway now keeps XDG_RUNTIME_DIR. In 0.5.0-alpha.7, a Hub started from a normal desktop or SSH login refused Fleet calls from your other computers ("The Fleet Hub session was reset").
• In-place upgrades. Installing a newer release into the same prefix and running teaa setup keeps your Fleet state and enrollment. Before, setup stopped and asked for a Fleet command that is not installed.

Also in this release line (0.5.0-alpha.7)

• Hub over FRA works end to end from your agent's own teaa mcp connection: tool calls from one computer are served by the Hub on another.
• teaa select-hub --account ORIGIN finds the connection between your two computers by itself; there is no Hub profile to write by hand.
• Reconnect: if the Hub restarts or the network drops, a call in progress returns a clear, retryable error (within about 25 seconds), and the same agent session reconnects by itself. ToolsEngine and Knowledge tools stay listed and available in the session meanwhile.
• Windows: the first teaa open no longer fails with a state-ownership error, whichever command you run first.

How it was tested

• Python not on PATH (alpha.6 and alpha.10): regression tests on Linux, and native Windows runs of both new archives with Python off PATH and set only through knowledge.command: setup, health check, tool calls (TEAA), Hub start, status and stop, a failed teaa open exiting with an error (TEAA + FRA + Hub), and an in-place upgrade from alpha.9.
• TEAA, Linux and native Windows: independent new-user QA of the exact archives: install, setup, health check, every tool call, a real Fleet worker job (Linux), and uninstall. The install guide was followed word for word on clean systems.
• TEAA + FRA + Hub, Linux: independent new-user QA of the exact archive against the self-hosted server package that this release's server differs from only in its SELF-HOSTING.md (a documentation correction; every other file is byte-identical). That covered sign-up with an emailed code; enrolling two computers through the account page; connecting them; Fleet calls served over FRA by the other computer's Hub; recovery in the same session after a Hub restart, after a network break, and after a call started during a network outage; a clean stop; and uninstall.
• TEAA + FRA + Hub 0.5.0-alpha.9, Linux, live: two real Linux computers were enrolled in a ToolsEnabled-hosted account, connected through toolsenabled.ai and upgraded in place from earlier builds; with each started from a normal login, Fleet calls on one computer were served by the Hub on the other while ToolsEngine and Knowledge stayed local. The same new-user and upgrade paths were also replayed in containers set up like a login session, including a Hub restart and a network break.
• TEAA + FRA + Hub, native Windows: independent QA of install, setup, health check, Hub start, status and stop, and the account connection step in both command orders. Natively, with no WSL.
• Self-hosted server: an independent security review of the server and its installer, plus a separate review of the account-page additions. SELF-HOSTING.md states exactly what each covered and what was not validated.

Known limitations

• Alpha software. Expect changes.
• No macOS build yet.
• Windows TEAA + FRA + Hub: tested natively up to connecting to an account. The full two-computer Hub-over-FRA journey was tested on Linux.
• Hosted accounts: the free tier allows up to 8 computers per account. Self-hosted servers have no ToolsEnabled limit.
• Self-hosted server: Linux (Ubuntu 24.04) only. It was tested with a local CA, mail sink and proxy; your own DNS, mail provider and proxy configuration are yours to validate.
• Fleet workers: they use your agent CLI and its plan. A large worker tree can use a lot of that plan; set Fleet's width and depth to suit.
• Payments: none. Everything in this release is free.