# Status

> Check whether Nowledge Mem is reachable and configured for ZCode, especially after setup or when memory operations fail.

- Skill: `nowledge-co/status-6` (Agent Skill)
- Install (CLI): `npx get-skill add nowledge-co/status-6`
- Raw SKILL.md: https://api.skillmd.com/api/skills/nowledge-co/status-6/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: nowledge-co (https://skillmd.com/u/nowledge-co)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/nowledge-co/status-6

---


# Status

Run a quick health check when the user asks whether Mem is working, when an operation fails, or after initial setup.

```bash
nmem --json status
nmem --json stats
nmem --json wm read
```

Interpret these separately:

- `status` reports reachability, mode, and server version;
- `stats` reports database statistics and memory count when available;
- `wm read` reports whether a Working Memory briefing exists;
- no memories or no briefing is different from a connection failure;
- do not print API keys or copy credentials into logs.

The CLI check and ZCode MCP check are separate diagnostics. A remote or custom ZCode MCP endpoint can be healthy even when the local CLI is not configured for the same server.

If the local CLI check fails:

1. **Local:** open the Nowledge Mem desktop app and retry.
2. **Remote CLI:** verify the URL and API key in the user's own `nmem` client configuration.

For the ZCode MCP path, use the server's status tool when it is available. For remote or custom Mem, generate the host-owned configuration, paste it into ZCode's own MCP settings, and reload the Agent runtime:

```bash
nmem config mcp show --host zcode
```

Do not treat a local `nmem --json status` failure as proof that the ZCode MCP server is unavailable, or vice versa.

