Skip to content

hylouis233/minimax-code-trajectory

v0.1.0Apache-2.0

Inspect local MiniMax Code session ledgers as privacy-aware, read-only trajectories through a dependency-free MCP server.

GitHubOpen Website

MiniMax Code Trajectory

A privacy-aware, read-only trajectory inspector for local MiniMax Code sessions.

MiniMax Code stores canonical local session events under the active profile's v2/sessions/YYYY/MM/DD/<session>/ledger.jsonl. This Plugin turns those ledgers into bounded, structured summaries that an agent can use to explain a task timeline, inspect failures, count tool activity, and compare the display transcript with Pi history—without modifying the source files.

The design is inspired by icesixgod/codex-trajectory at commit 2f10022557bbc4ffefce1eb656ab2e09dd55ff0e. This implementation is written from scratch for the MiniMax Code v2 ledger contract and does not copy the reference project's UI or source code.

Try it

Use the minimax-code-trajectory skill to show a safe summary of my latest local MiniMax Code task.
Highlight failed states, tool activity, compactions, and token usage. Do not expose message text.

Expected result: the agent calls list_minimax_sessions and get_minimax_trajectory, then returns a chronological summary containing event kinds, timestamps, state, message/tool counts, and usage totals. Default summary mode never returns message text, tool arguments/results, absolute paths, or raw ledger records.

Capabilities

  • list_minimax_sessions — lists recent local session IDs and non-content metadata.
  • get_minimax_trajectory — reads one session or the most recently updated session and returns a structured trajectory.
  • minimax-code-trajectory Skill — tells the agent how to use the tools without widening the privacy boundary.

The public Agent Plugins 1.0 subset does not expose custom Plugin UI/App extensions, so v0.1 returns structured MCP output rather than bundling an interactive timeline.

Privacy levels

  • summary (default): no titles, message text, thinking, tool arguments/results, workspace paths, file IDs, hashes, or raw records.
  • full: must be explicitly requested by the user. It returns redacted, length-bounded text previews and tool names, but still excludes thinking, tool arguments/results, attachment bytes, raw record metadata, absolute paths, and secrets matched by the built-in redactor.

The MCP server never writes to the MiniMax Code data directory. It rejects symlinked session artifacts, ignores malformed active-tail JSONL, caps individual ledger lines at 2 MiB, and returns at most 1,000 event summaries per call. Manifest-only sessions whose ledger has already been removed are counted as unavailable and skipped when choosing the latest inspectable session.

Requirements

  • MiniMax Code with Agent Plugins 1.0 MCP support.
  • Node.js 22+ on PATH (the server uses only Node.js standard-library modules).
  • Local-runtime v2 session artifacts.

The data directory is resolved in this order:

  1. MINIMAX_DATA_DIR
  2. MAVIS_DATA_DIR
  3. ~/.minimax

MiniMax Code production normally uses ~/.minimax. Development/profile runs should launch the host with the matching MINIMAX_DATA_DIR or MAVIS_DATA_DIR; the Plugin deliberately does not scan other home-directory profiles.

Data and network

  • Reads only manifest.json and ledger.jsonl below the resolved <dataDir>/v2/sessions directory.
  • Does not read credentials, config.yaml, auth files, SQLite databases, assets, .env files, or arbitrary user-provided paths.
  • No network access, telemetry, subprocesses, installers, native binaries, or paid services.
  • Full-detail previews become part of the active MiniMax Code conversation, so users should request them only when that conversation is allowed to contain the underlying task text.

Development and verification

node --test plugins/hetaoBackend/minimax-code-trajectory/test/*.test.mjs
npm run check

The tests use an isolated temporary data directory and cover data-dir precedence, session discovery, summary/full privacy boundaries, secret redaction, malformed and oversized JSONL, symlink rejection, manifest-only sessions, event limits, and the real MCP stdio process boundary.

License

Apache-2.0. See LICENSE.