v0.5.17

What's Changed

• release: v0.5.17 — plugin release/update hardening by @Shooksie in #246

Full Changelog: v0.5.16...v0.5.17

v0.5.16

What's Changed

• release: v0.5.16 — daemon queue-dispatch reliability by @Shooksie in #245

Full Changelog: v0.5.15...v0.5.16

v0.5.14

What's Changed

• release: v0.5.14 by @Shooksie in #243

Full Changelog: v0.5.13...v0.5.14

v0.5.13

What's Changed

• release: v0.5.13 by @Shooksie in #242

Full Changelog: v0.5.12...v0.5.13

v0.5.12

Full Changelog: v0.5.11...v0.5.12

v0.5.11 — Chat streaming fidelity + full provider matrix

v0.5.11 — Chat streaming fidelity + the full provider matrix

animus chat send --stream --json now streams everything the agent does, and all four provider tools (claude / codex / opencode / gemini) were brought up to current-CLI compatibility so their tool/command activity streams too.

Fixed (CLI)

• chat tool_result streams the tool output — previously emitted only success: bool, dropping the content. Now carries the provider's full output (command stdout, file contents, structured JSON).
• chat tool_result reports the human tool name — correlates a toolu_… id back to the preceding tool_call's name.

Provider compatibility — run animus plugin update

The provider plugins evolved past their parsers as the upstream CLIs changed. All released at v0.2.4 on the stable v0.1.13.2 protocol lineage:

• codex v0.2.4 — codex emits sandbox shell runs as command_execution items (not function_call); these were dropped. Now mapped to tool_call + tool_result.
• opencode v0.2.4 — opencode v1.2 wraps frames as {type, part} with tool details under part.state; parser read old keys → unknown_tool. Now parses the part shape (old format still handled).
• gemini v0.2.4 — gemini CLI refused headless runs in an untrusted directory (exit 55); provider now sets GEMINI_CLI_TRUST_WORKSPACE=true on spawn.

All four providers verified end-to-end through animus chat against official signed builds.

Full Changelog: v0.5.10...v0.5.11

v0.5.10 — Animus Chat (CLI-first)

v0.5.10 — Animus Chat

Multi-turn conversations through the CLI, streamed as JSON, built on the existing provider plugins (claude/codex/gemini) — no new plugin, no new API key.

Added

• animus chat new|send|get|list — durable multi-turn conversations. send --stream --json emits one ChatStreamEvent per line to stdout (turn_started / text_delta / tool_call / tool_result / metadata / turn_completed) — the surface to build chat apps on.
• animus cost conversation <id> — per-conversation token + USD rollup.
• Provider-owned continuity — each turn is resume XOR replay, never both: with a live provider session_id the prompt is just the new message (the CLI tool's native session carries history); with no session, Animus replays its stored transcript. Single full-history retry on stale-session. No double-counted context.
• Conversation store at ~/.animus/<repo-scope>/chat/<id>/ (meta.json + append-only messages.jsonl), path-traversal-guarded. User message persists before the provider call (crash safety); the provider's native session_id is captured per turn.
• Reuses SessionBackendResolver (the animus agent run path), so the wrapped CLI tool reaches Animus's MCP server via mcp_endpoint — the model can call animus.* tools mid-conversation.

Verified end-to-end

A two-turn conversation against the claude provider: turn 1 (resumed=false) streamed thinking + tool calls + reply; turn 2 (resumed=true, same session_id) correctly recalled context from the resumed native session. Transcript + cost rollup persisted.

Deferred to v0.5.11

Direct-API chat_provider plugins (own the turn structure, intercept tool use) and the OpenAI-compat HTTP surface. The turn loop is factored behind a TurnProducer seam so that path is additive. See docs/architecture/animus-chat.md.

Full Changelog: v0.5.9...v0.5.10

v0.5.9

Full Changelog: v0.5.8...v0.5.9

v0.5.8

Full Changelog: v0.5.5...v0.5.8

v0.5.5 — authoring ergonomics + governance + protocol cleanup

Highlights

This release ships seven authoring-side features, two architectural design proposals, a docs sweep for previously-hidden YAML blocks, and a v0.5.7 protocol-cleanup cluster.

Added

• worktree: block at workflow + per-phase level with mode: auto|required|skip, cleanup, base_ref. Replaces implicit, always-on worktree creation.
• secrets: block + ${secret.<name>} interpolation. Compile-time resolution, required-but-unset fails with file + line.
• Sensitive-interpolation lint. Warns on ${VAR} for env vars matching TOKEN|KEY|SECRET|PASSWORD outside the secrets: block.
• Trigger plugin authoring story. animus plugin scaffold trigger <name> + examples/triggers/fswatch/ reference plugin + authoring guide.
• Kernel-level OAuth broker for HTTP MCP servers. oauth: block with client_credentials / refresh_token / manual_bearer flows; 0600 cache, 60s skew margin, no token leakage.
• Basic eval framework. evals: block on phases with command + llm_judge checks, pass_threshold, on_fail: rework|block. Schema lands; runtime enforcement deferred to the out-of-tree workflow-runner plugin pin bump.
• Budget caps + animus cost CLI. Per-workflow + per-phase budget: block (max_tokens, max_cost_usd, on_exceed); cost-state aggregator + 4 animus cost subcommands.
• animus plugin doctor subcommand showing every preflight role with its installed claimants.
• animus plugin install --as-kind <KIND> + auto-increment on collision. Daemon-side translator rewrites <installed_kind>/<verb> to <native_kind>/<verb> so plugins stay unmodified.
• animus subject delete --kind <K> --id <ID> --yes CLI verb.

Architecture proposals (design only)

• docs/architecture/multi-tenant-rbac-v0.5.5.md — four-chokepoint RBAC scaffold; v0.6 implementation path.
• docs/architecture/knowledge-rag-binding-v0.5.5.md — memory plugin binding shape; references the already-published animus-memory-store-protocol v0.1.0.

Docs sweep

• schedules: + triggers: + daemon: blocks documented in workflow-yaml.md — features had shipped but were undocumented.
• Plus animus-plugin-template subject pin v0.1.0 -> v0.5.7.

Protocol cleanup (v0.5.7)

• launchapp-dev/animus-protocol v0.5.7 restores METHOD_SUBJECT_DELETE, SubjectBackend::delete default impl, BackendError::Unsupported, subject_backend_main helper. Fixes the v0.1.14 'sync' regression that silently wiped these surfaces.
• launchapp-dev/animus-subject-default v0.1.4 + animus-subject-requirements v0.1.8 + animus-subject-linear v0.1.5 released with SubjectBackend::delete implementations. Linear also carries a real data-loss bug fix (update with patch.comment was overwriting issue descriptions).

Plugin-org maintenance

• All canonical Rust plugins now have published binary assets for Linux x86_64 + Linux aarch64 + macOS aarch64 + macOS x86_64 (Intel runner queue stuck-job issue resolved by switching to macos-15-intel runner label; aarch64-linux switched from cross-rs to native ubuntu-24.04-arm runner).
• New launchapp-dev/animus-tui v0.1.0 standalone TUI control plane (k9s-style; 7 views; ratatui + crossterm + tokio + animus-control-protocol).

Carried forward to v0.5.8

• animus plugin rename <name> --to <new-kind> for post-install rename.
• 2 TODO(codex-p2) items in the kind translator (multi-kind subject backends, --name install override edge cases).
• animus-subject-linear + animus-subject-sentry protocol pin bump to v0.5.7.

See CHANGELOG.md for the full diff.

Full Changelog: v0.5.4...v0.5.5