---
name: Remnic Status
slug: remnic-status
category: Automation
description: Remnic Status checks whether the Remnic daemon, stores, and connected clients are healthy. Use it when recall or store calls fail, or when you need to confirm the daemon is running.
github: "https://github.com/joshuaswarren/remnic/tree/main/packages/plugin-claude-code/skills/remnic-status"
language: TypeScript
stars: 193
forks: 23
install: "npx degit https://github.com/joshuaswarren/remnic/tree/main/packages/plugin-claude-code/skills/remnic-status ~/.claude/skills/remnic-status"
installs_to: ~/.claude/skills/remnic-status
source_path: packages/plugin-claude-code/skills/remnic-status/SKILL.md
collection_size: 12
category_size: 2032
collection_url: "https://dirskills.com/collections/joshuaswarren/remnic"
added: 2026-09-06T05:19:10.302Z
last_synced: 2026-09-06T05:19:10.302Z
canonical_url: "https://dirskills.com/skills/remnic-status"
---

# Remnic Status

Remnic Status checks whether the Remnic daemon, stores, and connected clients are healthy. Use it when recall or store calls fail, or when you need to confirm the daemon is running.

**Install:**

```bash
npx degit https://github.com/joshuaswarren/remnic/tree/main/packages/plugin-claude-code/skills/remnic-status ~/.claude/skills/remnic-status
```

## README

## When to use

Use when the user asks whether Remnic is running, when recall or store calls start failing, or when diagnosing cross-agent memory issues from Claude Code.

Triggers:

- "Is Remnic running?"
- "Check memory status."
- `/remnic:status` slash command invocation.
- Recall/store tools returned connection errors in this turn.

## Inputs

- Optional: specific component to check (daemon, HTTP server, MCP server, store backend).

## Procedure

1. Check the Remnic health endpoint via the MCP bridge or run `remnic daemon status` in a shell.
2. Report, in a compact block:
   - Daemon running state (PID if known).
   - Listening port(s).
   - Memory store path.
   - Connected clients or plugins, if exposed.
3. If the daemon is not running, suggest `remnic daemon start` and mention the log path.
4. If recall/store tools were erroring earlier in the turn, correlate the health state with those errors in one sentence.

## Efficiency plan

- One health call per turn is enough; do not poll.
- Skip the check for trivially local tasks.
- Reuse the health payload for downstream troubleshooting within the same turn.

## Pitfalls and fixes

- **Pitfall:** Running `remnic daemon status` on a host where the daemon lives in a container. **Fix:** Prefer the MCP health endpoint, or run the CLI inside the container.
- **Pitfall:** Reporting "down" from a single failed tool call. **Fix:** Confirm with the health endpoint before claiming an outage.
- **Pitfall:** Forgetting the log path. **Fix:** Always include a pointer to logs on failure.

## Verification checklist

- [ ] Health was checked via the endpoint or CLI, not guessed.
- [ ] Daemon state, port, store path, and clients were reported concisely.
- [ ] If unhealthy, the user got a concrete next step.
- [ ] Canonical `remnic daemon` wording was used over legacy `engram daemon` where the CLI has been renamed.

> CLI names: canonical CLI is `remnic daemon`. The legacy `engram daemon` invocation remains accepted during v1.x.