Give Hermes Agent Permanent Memory

If HTTP is blocked in your network, use the stdio transport via the npm package:

{
  "mcpServers": {
    "agentbay": {
      "command": "npx",
      "args": ["-y", "aiagentsbay-mcp@latest", "--api-key", "ab_live_YOUR_KEY"]
    }
  }
}

Stores the API key in the config. Prefer HTTP transport when possible.

Tell Hermes to use memory proactively. If Hermes supports a system prompt, instructions file, or skill definition, add the following:

# AgentBay Memory Protocol

You have AgentBay MCP connected for persistent memory across sessions.

## On every session:
1. At session start, call agentbay_memory_recall with a query about
   the current task to load prior context.
2. Work on the task.
3. After meaningful work, call agentbay_memory_store to save what you
   learned.

## What to store:
- type="PATTERN": "This codebase uses X for Y"
- type="PITFALL": "Do not do X because Y breaks"
- type="DECISION": "We chose X over Y because Z"
- type="ARCHITECTURE": "Service A talks to B via C"

## What NOT to store:
- Raw code (it is in git)
- Temporary debugging state
- Secrets or credentials

## For shared project memory:
Use agentbay_memory_store and agentbay_memory_recall with a projectId
to share knowledge across agents and team members.

A versioned copy of this template is available at packages/hermes-plugin/memory-protocol.md.

Start a new Hermes session and test the round trip:

# In Hermes:
> Store a test memory titled "hermes verification" with content
  "AgentBay is connected to Hermes." Then recall it. Tell me which
  search strategies found the result.

# Hermes should call:
#   agentbay_memory_store → stores the test memory
#   agentbay_memory_recall → reads it back
#   The result should include strategies (fts, tag, vector, alias)

Code-aware recall across sessions: Hermes opens a project and asks what we know.

# Day 1 — working on auth middleware
> What do we know about auth middleware?

  agentbay_memory_recall query="auth middleware"
    → Auth pitfall (PITFALL, 91%): Always validate JWT expiry,
      not just signature
    → Auth pattern (PATTERN, 85%): JWT with 24h refresh tokens

> I found a race condition in the token rotation handler. Store this.

  agentbay_memory_store
    title="Token rotation race condition"
    type="PITFALL"
    content="Concurrent refresh requests can issue two valid tokens.
             Use Redis lock on the refresh token ID."
    tags=["auth", "jwt", "concurrency"]

# Day 7, new session
> Anything we should know about JWT?

  agentbay_memory_recall query="JWT"
    → Token rotation race condition (PITFALL) ← the learning from day 1
    → Auth pitfall: always validate expiry
    → Auth pattern: 24h refresh tokens