Step Code × Nowledge Mem
Start Step Code with your current context and keep completed coding conversations searchable across every connected tool.
For your agent
Read https://mem.nowledge.co/SKILL.md and follow the instructions to install or update Nowledge Mem for Step Code. Verify with nmem status and the Context Bundle or Working Memory check, start a fresh Step Code session, and confirm a completed exchange appears in nmem t list --source step-code.step install npm:nowledge-mem-step-codeThe dedicated package uses Step Code's native extension and skill system. It gives Step Code your current Mem context before work begins, then saves completed conversations with their own step-code provenance.
Before You Start
- Nowledge Mem App is running, or this machine is connected to a remote Mem server
- Step Code is installed
nmem statussucceeds in the shell that launchesstep
Install and Verify
step install npm:nowledge-mem-step-codeRestart Step Code. In a new session, ask it what Nowledge Mem context it received. The answer should use the injected Context Bundle or Working Memory without rereading it.
To update only the Nowledge Mem package later:
step update npm:nowledge-mem-step-codeComplete one short user and assistant exchange, then check:
nmem t list --source step-code -n 5How Capture Works
Step Code can retry, compact, or continue automatically after an individual model run. The connector waits for Step Code's agent_settled lifecycle event, when those continuations are finished, before scheduling a thread write. It also performs bounded final flushes before compaction, session switches, and shutdown.
The package reuses the same checkpointed delta engine as the Pi connector, but Step Code remains a separate source. Do not install nowledge-mem-pi as the Step Code connector: its source identity and history root are different.
Import Older Sessions
Automatic capture begins after the package is installed. To backfill older native Step Code sessions, preview first:
nmem t sync --from step-code --limit 20Then import:
nmem t sync --from step-code --applyThe importer reads ~/.stepcode/agent/sessions by default and honors STEP_CODING_AGENT_SESSION_DIR or STEP_CODING_AGENT_DIR. Use --session-dir for an explicit custom root. Session and entry IDs are stable, so rerunning the command updates the same threads instead of creating copies.
App and Remote Mem
For the local App, no endpoint configuration is needed. Keep the App running and make sure nmem status reports ok.
For a remote or Cloud destination, configure this machine once:
nmem config client set url https://your-server
nmem config client set api-key your-key
nmem statusThe extension and history importer use the same client configuration. NMEM_SPACE can pin an entire Step Code process to one Space; NMEM_AGENT_ID should only identify a durable agent role, not an ordinary one-off session.
Troubleshooting
Skills do not load. Run step list and confirm nowledge-mem-step-code is installed, then restart Step Code.
A completed conversation is missing. Confirm the exchange contains both a user and assistant turn, run nmem status, and enable NMEM_PLUGIN_DEBUG=1 only while diagnosing the extension.
Older sessions are missing. Run the preview command above on the machine where Step Code stores its JSONL files. A remote Mem server cannot scan that machine's home directory by itself.