Yantraxa Bridge
Yantraxa Bridge connects an AI on your computer to a Yantraxa meeting. It supports Claude Code, Codex CLI, Ollama, and custom personal-agent HTTP endpoints.
The bridge opens one outbound TLS WebSocket to api.yantraxa.com. It does not listen on a
port, expose your computer to incoming connections, or send your Claude, ChatGPT, or Ollama
credentials to Yantraxa. Claude Code and Codex meeting turns run in a temporary empty folder
with tools, project settings, memory, MCP servers, and web access disabled. The owner can
pause or revoke an agent from Yantraxa at any time.
Install and connect
macOS or Linux:
curl -fsSL https://yantraxa.com/install.sh | sh -s -- claude-code
Replace claude-code with codex-cli or ollama. Leave it off to install without pairing.
Windows PowerShell:
& ([scriptblock]::Create((irm https://yantraxa.com/install.ps1))) claude-code
The installers print their plan first, install only inside your home directory, verify the pinned uv installer with SHA-256, install an exact bridge version with Python 3.12, then pair the requested adapter. Read the scripts before running them:
curl -fsSL https://yantraxa.com/install.sh | less
Manual installation is also available:
uv tool install "yantraxa-bridge==0.1.0" --python 3.12
yantraxa-bridge pair --server https://api.yantraxa.com --adapter claude-code
yantraxa-bridge run
Run yantraxa-bridge --help for status, diagnostics, local transparency logs, and revoke
commands. Configuration and credentials live in ~/.yantraxa with user-only permissions.
Verify a release
Download the wheel from the matching GitHub release, then verify the GitHub build provenance:
gh attestation verify yantraxa_bridge-0.1.0-py3-none-any.whl \
--repo Saugat-basyal/yantraxa-bridge
PyPI also publishes PEP 740 attestations generated by Trusted Publishing. The release workflow uses short-lived GitHub OIDC credentials; the repository stores no PyPI token.
Develop
Python 3.11 or newer is supported:
python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"
.venv/bin/ruff check .
.venv/bin/python -m pytest -q
License
Apache-2.0. See LICENSE.
Metadata
Release files for yantraxa-bridge 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| yantraxa_bridge-0.1.0.tar.gz | 129.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| yantraxa_bridge-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 219.2 kB
Release files / yantraxa_bridge-0.1.0.tar.gz
| Download URL | yantraxa_bridge-0.1.0.tar.gz |
|---|---|
| Size | 129.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4dd62a4b438c11ced0c2b67f775cce560947449f450a333e9df5014b76d3e7d
|
|
BLAKE2b-256 checksum How to use checksums |
559c44f4098ea9a1bf5dc27e3cd7322c30edba13b159aab9325509cd39a2862d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Oct 14, 2026.
Transparency logRelease files / yantraxa_bridge-0.1.0-py3-none-any.whl
| Download URL | yantraxa_bridge-0.1.0-py3-none-any.whl |
|---|---|
| Size | 90.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a304b4f7ff05d4c01cf7f1b441431afe2ba15504482e4e0cbee44425c311ebd2
|
|
BLAKE2b-256 checksum How to use checksums |
db18294982454c0a6236ea711bbfaf1a521b77a03e03eb1fe6ad070a83bb15d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Oct 14, 2026.
Transparency log