Skip to the content
hippo
Contents
  1. Introduction
  2. Install
  3. Quick start
  4. Concepts
  5. Architecture
  6. Packs
    1. Writing a pack
    2. First-party packs
    3. The registry
    4. Themes
  7. Commands
  8. Configuration
  9. Sharing a brain in a team
  10. Scheduling on macOS
  11. Measuring with hippo eval
  12. Troubleshooting with hippo doctor
  13. Security and privacy
  14. Roadmap
  15. Limits and known gaps
  16. Contributing and licence

Roadmap

This is version 0.4.1. hippo is one person’s project, so there are no dates here. “Planned” means I intend to do it and know roughly how. “Idea” means it is not designed yet and may not happen.

The text lives in ROADMAP.md at the root of the repository, and the docs site shows the same file. How the built parts work is in Architecture; what is missing or rough today is in Limits and known gaps.

What is built

  • The core and CLI: an index of Claude Code, Codex, DeepSeek Harness (dsh), OpenCode, Muse Code and Command Code transcripts, recall and ask, the overview, fleet, incidents, xray and card.
  • An adapter for DeepSeek Harness (dsh): its session logs, compressed or not, with sub-agents and forks (design).
  • An adapter for OpenCode: OpenCode 2’s SQLite database, read-only and session by session, with sub-agents and forks (design).
  • An adapter for Muse Code: its session logs, as Muse 1.4.18 writes them (design).
  • An adapter for Command Code: its version 3 session files (design).
  • Notes, context, and hooks for Claude Code and Codex.
  • Dreaming with a fresh-context reviewer, receipts, snapshots and revert, and its schedule: launchd on macOS, printed cron and systemd lines elsewhere.
  • hippo eval with a synthetic question set.
  • Packs: hippo add and hippo packs, the registry tool and its static site, and 26 first-party packs (23 pass packs and 3 theme packs), all reviewed and listed in the registry.
  • A Claude Code plugin, an install script, release binaries for macOS and Linux, and a Homebrew formula attached to the release.
  • A DeepSeek Harness (dsh) plugin, installed from GitHub: the start block in each new session, and hippo_ask and hippo_day as tools (design).
  • An OpenCode plugin, installed from GitHub: the start block in the system prompt of each top-level session, and hippo_ask and hippo_day as tools (design).
  • The desktop app, Hippo.app: macOS only, built from source, early, and checked on synthetic data.
  • The community feed server (crates/hippo-feed): built and tested locally, not deployed. See docs/feed-local.md.

Planned

  • Adapters for more agents. Cursor and Gemini folders are detected but not read. Reading them is the next adapter work. An adapter needs a redaction test before it lands.
  • Measuring whether dreaming helps. hippo eval measures a small invented set. It does not show whether the nightly pass makes an agent’s work better on real notes. I want a measurement that does, before claiming it.
  • Packs by other authors. The registry takes outside entries today (registry/README.md). None exists yet.
  • Deploying the community feed. The server is built and tested locally. Nothing is hosted.
  • Signed and notarised macOS builds. Neither the release binaries nor Hippo.app are signed with a Developer ID or notarised. The app is signed ad hoc, so its first launch needs Open Anyway in System Settings.
  • Hippo.app beyond synthetic data. The app is checked on synthetic data only. The next step is using it day to day and fixing what that shows, before calling it more than early.

Ideas

  • Hosted dreaming, live team sync of a shared brain, and private packs. Not designed in public yet. Today a team shares a brain through git (Sharing a brain in a team).

To suggest something, open an issue. A new feature or contract starts as a design doc in docs/designs/ before any code.