tareslisted

# Tares Install and connect **Tares** (docs: https://docs.glassflow.ai/tares). Tares puts every event from a user's systems on one timeline per thing, wakes an agent when a trigger fires, and keeps the finding for the next reader. This skill takes a machine from nothing to: daemon running, one source receiving, this agent connected over MCP, one successful `read`. ## Operating rules - Act autonomously once the user asks for Tares to be installed. Ask only for what you cannot infer: which source to add first, and its one or two parameters (see step 4). - Say what is about to run and that it may take a while. `uv tool install` can take a minute; post a line of progress while it runs so the user does not kill it. - Print each command and its result. If a command fails, change something before retrying. - Never paste secrets into the console, the chat, or a file you show. Read them from environment variables (`GITHUB_TOKEN`, `ANTHROPIC_API_KEY`). A variable exported only in your shell is not seen by a `tares up` started elsewhere; start the daemon from the shell that has it, or tell the user to set it where the daemon runs. - Do not create what already exists: `GET /api/sources` first, and skip a source whose name is taken. - Everything below goes through the HTTP API at `http://127.0.0.1:8787`, not the console. The console is for the user afterwards. ## 1. Prerequisites ```bash uv --version || pipx --version # one of the two; stop and tell the user how