Octopoda Memory

Created By
RyjoxTechnologies2 months ago
Persistent memory for AI agents that survives across sessions. Store, recall, and semantically search memories. Includes loop detection that catches agents stuck repeating themselves, full audit trails, shared memory between agents, and a real-time dashboard. Works with Claude Code, Claude Desktop, and Cursor. Open source, free tier available.
Overview

Octopoda Memory

Persistent memory for AI agents. Store, recall, and search memories that survive across sessions.

Features

  • Persistent Memory — agent.remember() and agent.recall() that survives restarts, crashes, deployments
  • Semantic Search — find memories by meaning, not just exact keys
  • Loop Detection — catches agents stuck repeating themselves before they burn tokens
  • Audit Trail — every decision logged with reasoning
  • Shared Memory — agents share knowledge through memory spaces
  • Real-time Dashboard — monitor all agents at localhost:7842

Setup

  1. Install: pip install octopoda
  2. Get free API key at https://octopodas.com
  3. Add to Claude Code: claude mcp add octopoda -s user -e OCTOPODA_API_KEY=your-key -- python -m synrix_runtime.api.mcp_server

13 Tools Available

  • octopoda_remember — store a memory
  • octopoda_recall — get a memory by key
  • octopoda_recall_similar — semantic search
  • octopoda_search — prefix search
  • octopoda_recall_history — version history
  • octopoda_snapshot / octopoda_restore — checkpoint and rollback
  • octopoda_share / octopoda_read_shared — shared memory between agents
  • octopoda_list_agents — list all agents
  • octopoda_agent_stats — performance stats
  • octopoda_log_decision — audit trail
  • octopoda_loop_status — loop detection

Server Config

{
  "mcpServers": {
    "octopoda": {
      "command": "python",
      "args": [
        "-m",
        "synrix_runtime.api.mcp_server"
      ],
      "env": {
        "OCTOPODA_API_KEY": "your-key-from-octopodas.com"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
RyjoxTechnologies
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago