Skip to content

v0.8.0 — Open source: one-command install, LOCOMO benchmark, MIT

Choose a tag to compare

@fonsecabc fonsecabc released this 04 Aug 04:08
· 8 commits to main since this release

Install it in one command

The setup driver is agent-first — hand it to Claude Code and it stands Tars up itself:

curl -fsSL https://raw.githubusercontent.com/fonsecabc/tars/main/install.sh | bash

install.sh is dependency-free and idempotent: it clones (or updates) the repo and hands off
to tars init, which provisions any of four components — the engine, an always-on
service
, the Claude Code MCP registration, and a personalized persona — then prints a
JSON summary an agent reads to continue. Run it headless with
--all --owner-name "Ada" --install-prompt --yes --json.

Also new: a bin/tars CLI, a Dockerfile, and deploy/docker/docker-compose.full.yml for a
one-command Postgres + server stack.

Benchmarked on LOCOMO

Retrieval now has numbers instead of vibes. packages/core/src/eval/locomo/ ingests all ten
LOCOMO conversations as verbatim, timestamped observations and answers strictly from what
memory_recall returns.

  • Retrieval hit-rate 82.9% over the 1,540 answerable questions (81.3% across all 1,986,
    including the 446 adversarial ones where abstaining is the correct behavior).
  • Answer accuracy 48.4% → 54.6%, temporal questions 4% → 27.1%, adversarial abstention
    90.4% → 92.4%.
  • The temporal jump was a rendering fix, not a retrieval one. Every observation already
    carried an absolute validFrom; it just wasn't surfaced. Prefixing each recalled line with
    its bracketed date was the entire change.

The harness runs fully local (qwen2.5:14b answers, 32b judges, nomic-embed-text embeds),
so answer accuracy is capped by a small model — the hit-rate is the model-independent
number, and these figures are for comparing Tars configurations against each other, not against
leaderboard scores judged by frontier models. Reproduce with
packages/core/src/eval/locomo/download.sh.

Chronicle — one shared session log

Every harness — Claude Code sessions, cron routines, the voice loop — now writes to a single
loopback session log, so they can see and message one another.

  • Transactional store + ops layers over a new sessions migration, lane-gated.
  • Harness adapters: Claude Code shadow tailer, cron recorder, voice capture.
  • Inter-session message and signal lanes with per-session inboxes.
  • /watch — a live dashboard served on the loopback listener.

Loopback-only by design. Don't expose it.

The voice stack is public

The always-on voice loop (mic → whisper → router → speak) now ships owner-configurable, with
personal paths and data scrubbed out.

MIT

Relicensed to MIT.

Also

  • com.tars.janitor process-hygiene agent, plus a cloud deploy scaffold (deploy/cloud/) with
    restic backups.
  • Hermetic tests for the embedding providers, rerank client, and env config; coverage reporting
    and a .gitleaks.toml.

115 files changed, +13,135 / −364.