raymon

Stateful HTTP ingest + MCP server + terminal UI for Ray-style logs.

Raymon is:

• CLI-first: one binary, local-first defaults.
• MCP-first: a small set of tools with explicit schemas for agents/LLMs.
• Keyboard-first: a Ratatui TUI designed for fast filtering, yanking, navigation and export.

Installation

Cargo (crates.io)

cargo install raymon

Homebrew

brew install bnomei/raymon/raymon

GitHub Releases

Download a prebuilt archive from the GitHub Releases page, extract it, and place raymon on your PATH.

From source

git clone https://github.com/bnomei/raymon.git
cd raymon
cargo build --release

Quickstart

Sending Logs

You can send from any compatible Ray App library such as PHP, Javascript, Bash, Ruby, Python, Go and Dart.
If you want a Rust-native way to send Ray-compatible payloads, use my companion library ray-dbg.

Run Raymon locally with TUI

Run Raymon on the Ray default port:

raymon
# or
RAYMON_PORT=23517 raymon

Demo mode (self-generates events):

raymon --demo

TUI<-->MCPs (Streamable HTTP)

1. Start your local HTTP with TUI listening to default port 23517

raymon

1. Add the local HTTP to the agents harness via MCP settings:

codex mcp add raymon --url http://127.0.0.1:23517/mcp

{
  "mcpServers": {
    "raymon": {
      "url": "http://127.0.0.1:23517/mcp"
    }
  }
}

Remote (Streamable HTTP)

1. Start Raymon (recommended: require + send auth)

export RAYMON_AUTH_TOKEN="change-me"
RAYMON_ALLOW_REMOTE=1 RAYMON_HOST=0.0.0.0 RAYMON_NO_TUI=1 RAYMON_AUTH_TOKEN="$RAYMON_AUTH_TOKEN" raymon

Raymon will refuse non-loopback binds without RAYMON_AUTH_TOKEN unless you set RAYMON_ALLOW_INSECURE_REMOTE=1.

1. Add it to your MCP client:

codex mcp add raymon --url http://<host>:23517/mcp --bearer-token-env-var RAYMON_AUTH_TOKEN

{
  "mcpServers": {
    "raymon": {
      "url": "http://<host>:23517/mcp"
    }
  }
}

HTTP Endpoints

• POST /: Ray ingest endpoint (Ray payload envelope).
  • If the request body looks like JSON-RPC ({"jsonrpc":"2.0","method":...}), Raymon will treat it as MCP.
• POST /mcp: MCP Streamable HTTP endpoint.

MCP Tools

Raymon exposes an intentionally small tool surface so it stays usable for agents.

Tools and their input/output shapes:

• raymon.search - search stored entries (supports limit + offset)

  Parameters:

  {
    "query": "string (optional; plain text or /regex/)",
    "types": ["string"],
    "colors": ["string"],
    "screen": "string (optional)",
    "project": "string (optional)",
    "host": "string (optional)",
    "limit": "number (optional)",
    "offset": "number (optional)"
  }
  

  types and colors also accept comma-separated strings, e.g. { "types": "error,exception" }.

  Result:

  {
    "entries": [
      {
        "uuid": "string",
        "received_at": "number",
        "project": "string",
        "host": "string",
        "screen": "string",
        "payload_count": "number",
        "payload_types": ["string"]
      }
    ],
    "count": "number",
    "limit": "number",
    "offset": "number"
  }
  

  count is the total number of entries matching the filters (ignores limit/offset).

• raymon.get_entries - fetch entries by UUID(s)

  Parameters:

  { "uuids": ["string"] }
  

  Fallback (legacy/single): { "uuid": "string" }.
  String values also accept comma-separated UUIDs: { "uuids": "id-1,id-2" }.
  In comma-separated string form, whitespace in each UUID token is ignored.

  Result:

  {
    "entries": [
      {
        "uuid": "string",
        "received_at": "number",
        "project": "string",
        "host": "string",
        "screen": "string",
        "session_id": "string (or null)",
        "payloads": [
          {
            "type": "string",
            "content": "any",
            "origin": {
              "project": "string",
              "host": "string",
              "screen": "string (or null)",
              "session_id": "string (or null)",
              "function_name": "string (or null)",
              "file": "string (or null)",
              "line_number": "number (or null)"
            }
          }
        ]
      }
    ]
  }
  

Skill

This repo includes a skill at skills/raymon/SKILL.md (an AI-facing runbook, not runtime code) that teaches an agent how to:

• generate Ray-style events using the official/community Ray libraries (PHP, JavaScript, Bash, Ruby, Rust, Python, Go, Dart),
• connect to Raymon locally or remotely (with auth) and add it as an MCP server, and
• use raymon.search → raymon.get_entries to triage logs and extract high-signal context (uuid, payload types, origin file/line).

TUI

The TUI is intentionally "editor-like" (vim-ish):

• ? opens keybindings/help.
• q quits (and shuts down the HTTP/MCP server).
• Space opens the pickers/filters modal.
• / searches (fuzzy, message + file; path-like queries are literal), r opens regex search (message + file).
• : searches inside detail (jq).
• J/K or PageUp/PageDown scrolls the detail pane.
• s snaps the color + type filters to the selected log entry.
• p pauses/resumes live updates.
• x archives the current view (writes a new archive file).
• n (in the Archives pane) renames the selected archive file (confirm with Enter; Esc cancels; live cannot be renamed).
• d (in the Archives pane) deletes the selected archive (confirm required; live cannot be deleted).
• y yanks the selected list entry, Y yanks the detail pane.
• z toggles JSON expanded/collapsed (default: expanded), Z toggles raw JSON.
• u resets search + filters (screens/types/colors).
• Ctrl+y pastes the yank register into inputs.
• Ctrl+l clears the live log list (does not delete stored entries).
• 1 toggles color dot, 2 timestamp, 3 type label, 4 file, 5 message, 6 uuid (short).
• o opens the origin in your IDE (see RAYMON_IDE), e opens the detail in $EDITOR via a temp file.
• In the Archives pane, Enter loads the selected archive; the green ‣ row returns to live (◼ = active archive, ◻ = inactive).

Theming

Raymon sticks to the terminal's ANSI palette (16 colors + text attributes like bold/dim/reverse), so it inherits your terminal theme (light/dark, base16, etc)without implementing full app theming. You can also enforce a set of colors via an RAYMON_TUI_PALETTE environment variable.

Configuration

Raymon is configured primarily via environment variables:

Raymon also supports a ray.json config file (searched from the current directory upwards). Keys mirror env vars (e.g. host, port, tui, max_entries, storage_max_entries). CLI flags override env and file config.

Local Pre-commit

prek validate-config prek.toml
prek run --all-files
prek install

License

MIT. See LICENSE.