From openltm
Manages the LTM graph visualization server: start, stop, or check status of the force-graph UI at localhost:7332 viewing openltm.db.
How this skill is triggered — by the user, by Claude, or both
Slash command
/openltm:LtmServerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Obsidian-style force graph at **http://localhost:7332** visualizing `openltm.db`.
Obsidian-style force graph at http://localhost:7332 visualizing openltm.db.
| Detail | Value |
|---|---|
| UI (Next.js) | :7332 — open this in browser |
| API + WebSocket | :7331 — Next.js proxies /api/* here |
| PID file | ~/.claude/tmp/ltm-server.pid |
| Log file | ~/.claude/tmp/ltm-server.log |
| Server | ${CLAUDE_PLUGIN_ROOT}/src/graph-server.ts |
| UI source | ${CLAUDE_PLUGIN_ROOT}/graph-app/ |
| User says | Action |
|---|---|
| start / open / launch | → Workflows/Start.md |
| stop / kill / close | → Workflows/Stop.md |
| status / running? | Check PID file, report URL or "not running" |
PID_FILE="$HOME/.claude/tmp/ltm-server.pid"
if [ -f "$PID_FILE" ]; then
PID=$(cat "$PID_FILE")
if kill -0 "$PID" 2>/dev/null; then
echo "Running — PID $PID — http://localhost:7332 (Next.js) + http://localhost:7331 (API)"
else
echo "Not running (stale PID file)"
fi
else
echo "Not running"
fi
npx claudepluginhub rohirik/openltm --plugin openltmManages the full lifecycle of LangGraph applications: scaffold, develop locally with hot reload, build Docker images, and deploy to LangGraph Platform via CLI commands and langgraph.json config.
Starts a local dashboard server (Deno) for managing projects, viewing workflow graphs, agent streams, and documents. Useful for monitoring and managing multi-project workflows via browser.
Opens a read-only web UI to explore the kongcode memory graph via dashboard, memory/concept browsers, and graph explorer. Use for visualizing and inspecting stored data.