Metadata-Version: 2.5
Name: tuva
Version: 0.1.21
Summary: Tuva CLI — terminal interface to the Tuva daemon
Project-URL: Homepage, https://tuva.ai
Project-URL: Repository, https://github.com/Tuva-ai/entropy
Author: Tuva AI
License: Proprietary
Keywords: ai,research,tuva
Requires-Python: >=3.10
Requires-Dist: prompt-toolkit>=3.0
Requires-Dist: pydantic<3.0.0,>=2.5.0
Requires-Dist: rich>=13.7
Requires-Dist: typer>=0.12
Requires-Dist: uv>=0.5; platform_machine == 'x86_64' or platform_machine == 'x86' or platform_machine == 'AMD64' or platform_machine == 'aarch64' or platform_machine == 'arm64' or platform_machine == 'ARM64'
Requires-Dist: websockets>=14
Provides-Extra: dev
Requires-Dist: pytest-asyncio>=0.21; extra == 'dev'
Requires-Dist: pytest>=8; extra == 'dev'
Description-Content-Type: text/markdown

# tuva — Tuva CLI

Terminal interface to the Tuva daemon. Speaks the same protocol the VS Code
extension uses.

## Install

```bash
python3 -m pip install tuva       # Python 3.10+; on a cluster: `module load python/3.12` first
tuva                              # guided setup
```

The wheel depends on `uv`, which provisions the backend venv on the first `tuva start`;
there is no separate uv install. Full walkthrough: [`docs/QUICKSTART.md`](../docs/QUICKSTART.md).

## Install (dev)

```bash
pipx install -e ./cli
tuva --version
```

## Commands

| Command | Purpose |
|---|---|
| `tuva` / `tuva onboard` | Guided setup checklist; bare `tuva` shows status once set up (`--yes` for scripts) |
| `tuva start` / `tuva stop` | Bring the daemon up / down (idempotent) |
| `tuva status` | Show daemon health + ports, and each detected coding agent's Tuva MCP wiring (`--json` for scripts) |
| `tuva restart` | Stop + start |
| `tuva logs [-f]` | Tail `backend.log` |
| `tuva chat` | Interactive chat REPL against the daemon |
| `tuva init [<dir>]` | Initialize a project (`.project` file); local, no daemon needed |
| `tuva index <dir>` | Register + index a workspace for knowledge search |
| `tuva workspaces list/forget` | Inspect / drop registered workspaces |
| `tuva mcp` | List the coding agents found on this machine (Claude Code, Codex, Cursor, Claude Desktop) and toggle Tuva's MCP server for them |
| `tuva mcp status/configure/disable/repair` | The same, scriptable (`status --json`; `configure <agent>` works even for an undetected agent) |
| `tuva memory agent-sessions --list-projects` | Every folder on this machine with Claude Code / Codex sessions, and whether it's set up (`--json`) |
| `tuva feedback -m "…"` | Send a report to the Tuva team via the signed-in daemon (`--category`, `--metadata-json`) |

For the full startup walkthrough (backend venv, `TUVA_REPO_ROOT`, local-mode keys, idle behavior,
troubleshooting), see **Section 5 of the root [`README.md`](../README.md)**.

An unexpected failure prints "Something went wrong" and exits 1. The traceback goes to the file on
the error's Details line (`log/cli.log` in Tuva's state folder). `tuva --debug <command>` or
`TUVA_DEBUG=1` also prints it.

`tuva auth login/verify/logout/whoami` manages cloud-mode credentials; a caller with no terminal
uses `login --no-prompt --email <you>` and then `verify --email <you> --code -` with the code on
stdin (or in `TUVA_AUTH_CODE`), so it never sits in the process list.

## Run tests

```bash
cd cli
pip install -e '.[dev]'
pytest
```
