Ekko Agent x Nowledge Mem

Read https://mem.nowledge.co/SKILL.md and follow the Ekko Agent instructions. Verify Nowledge Mem MCP with nmem status, then preview transcript import with nmem t sync --from ekko before using --apply.

Ekko Agent is the agent runtime built into Hermes Studio. It can already use Nowledge Mem through MCP for Context Bundle, Working Memory, memory search/save, Library, and graph tools. MCP does not read Ekko's local conversation database, so exact thread capture is a separate local nmem import path.

Setup

Configure Nowledge Mem MCP inside Hermes Studio or the Ekko Agent host. Generate the host block from the same client settings used by nmem:

nmem config mcp show --host ekko

For remote Mem, configure this machine once before generating the MCP block:

nmem config client set url https://your-server
nmem config client set api-key your-key

Import Ekko Threads

Ekko writes completed run messages into its SQLite memory store at $HERMES_WEB_UI_HOME/.ekko/ekko.db. Preview first:

nmem t sync --from ekko

Import only after the preview shows the expected sessions:

nmem t sync --from ekko --apply

To import one known session:

nmem t sync --from ekko --session-id <session-id> --apply

If Hermes Studio uses a custom or development database path, pass it explicitly:

nmem t sync --from ekko --session-dir /path/to/ekko.db --apply

The importer reads memory_messages, keeps the human-facing user and assistant messages by default, and stores the result as source=ekko with a stable ekko-<session_id> thread id. It is safe to rerun; Mem appends only messages it has not already seen.

Current Boundary

Today this is a history and recovery importer. Automatic post-run capture should be triggered by Hermes Studio or Ekko after a completed run, using the same nmem t sync --from ekko --session-id ... --apply path or a future host capture adapter. A failed Mem import should never fail the Ekko run.

The desktop watcher does not poll Ekko's SQLite database in the background. Use nmem t sync --from ekko when you want to import local Ekko conversations.

Troubleshooting

nmem says ekko is unsupported. Update the CLI from the same source you installed it, then retry:

# Desktop: Settings -> Preferences -> Developer Tools -> Install CLI
python3 -m pip install --user --upgrade nmem-cli
# or: pipx upgrade nmem-cli
nmem --version

No Ekko sessions found. Confirm Hermes Studio has completed at least one Ekko run and that the database exists at $HERMES_WEB_UI_HOME/.ekko/ekko.db. If your install uses another path, pass that database with --session-dir.

The database is busy or unreadable. Close Hermes Studio and rerun the preview. If it still fails, pass the exact ekko.db path and check that the file is not corrupt.

MCP works but threads are missing. That is expected until you run the local importer. MCP provides memory/context tools; thread import must run on the machine that owns Ekko's SQLite database.

Sources

• Ekko memory store: packages/ekko-agent/src/memory/store.ts
• Ekko message types: packages/ekko-agent/src/memory/types.ts
• Ekko memory behavior note: 2026-07-10-ekko-agent-memory.md