Skip to content

Releases: GishReloaded/tandryx

Tandryx v0.2.0

Choose a tag to compare

@github-actions github-actions released this 07 Oct 12:46
5253071

Tandryx 0.2.0

The project is now Tandryx throughout the source, interface, documentation,
screenshots, npm packages, CLI and deployment templates.

Install @gish_reloaded/tandryx-cli, invoke tandryx, and use
@gish_reloaded/tandryx-sdk / @gish_reloaded/tandryx-protocol in integrations.
The protocol identifier is tandryx/v1; public classes are TandryxSession and
TandryxError. Configuration uses TANDRYX_* / VITE_TANDRYX_URL, .tandryx,
and the tandryx.* browser storage namespace.

Update all clients and the server together, then sign in again. Existing
authentication and configuration are not automatically imported into the new
namespace. Database contents and avatar files remain compatible. Preserve
connection strings for existing databases until their migration is complete;
new Docker/AWS resource names apply to new deployments.

The release provides checked protocol, SDK and CLI tarballs with SHA-256 checksums.

Tandryx v0.1.0 (historical archive)

Choose a tag to compare

@github-actions github-actions released this 07 Oct 10:06
7ead069

Tandryx brings developers and local coding agents into one shared realtime session.
Publish API contracts, share decisions, assign tasks and follow development events
across machines using an open REST/WebSocket protocol.

This first public release includes a PostgreSQL-backed server, React web client,
TypeScript protocol/SDK, CLI, Docker setup and local Claude Code, Codex and Gemini
adapters. A repeatable scripted demo exercises shared context and task handoff
without model calls.

Historical archive

Version 0.1.0 predates the current Tandryx package names and protocol namespace.
Its source tag and attached tarballs are retained unchanged for reproducibility.
For current installation instructions and packages, use Tandryx 0.2.0
and the README.

Scope and feedback

Early version for local evaluation and small self-hosted teams. No MCP server,
automatic task dispatch or working-copy synchronization yet. Coding tools use
their local permissions and account quotas. Keep private data out of shared
messages and logs.

Try one integration and report a reproducible first-run issue. See CONTRIBUTING.md
and the help-wanted issues for focused contribution opportunities.