Metadata-Version: 2.4
Name: hivespace
Version: 0.1.7.dev2
Summary: Hivespace CLI — talk to your team's Hivespace workspace from the terminal
License-Expression: Apache-2.0
Keywords: agents,workspace,cli,hivespace
Requires-Python: >=3.11
Description-Content-Type: text/markdown
Requires-Dist: typer>=0.15.0
Requires-Dist: click>=8.0
Requires-Dist: httpx>=0.28.0
Requires-Dist: rich>=13.0

# Hivespace CLI

Talk to your team's [Hivespace](https://hivespace.app) workspace from the
terminal — read and write the shared team drive, manage agents, and run
workflows.

```bash
uv tool install hivespace      # or: pipx install hivespace / pip install hivespace
hivespace auth login           # paste a personal access token from the web UI
hivespace --help
```

The CLI talks to `https://hivespace.app` by default; point it elsewhere with
`HIVESPACE_SERVER=https://your-host`.

This is a thin HTTP client (only `typer`, `click`, `httpx`, `rich`) — it does
not contain or run the Hivespace server.

## Honeycomb observability agent

Create an observability PAT in **Admin → Evaluation → Honeycomb**, then log the
agent's machine into the CLI:

```bash
hivespace auth login
```

The judged seed queue and its trajectory drill-down are available under
`hivespace observability`. Agent integrations should pass `--json`:

```bash
hivespace observability seeds list --status accepted --json
hivespace observability seeds get 123 --json
hivespace observability units get 456 --json
hivespace observability units search 456 --event-type tool_call --json
hivespace observability turns get 456 TURN_ID --raw --json
hivespace observability events get EVENT_ID --json
```

After reviewing a pending seed, a write-capable observability PAT can place it
in the Honeycomb queue explicitly:

```bash
hivespace observability seeds accept 123 --note "useful regression" --json
hivespace observability seeds reject 124 --note "not actionable" --json
```

After the Honeycomb task is successfully created, a write-capable
observability PAT can acknowledge consumption. Reading a seed never changes
its status, and failed downstream work must not be acknowledged:

```bash
hivespace observability seeds export 123 \
  --metadata '{"honeycomb_task_id":"hc-123"}' --json
```
