Troubleshooting
Quick checks (try these first)
Section titled “Quick checks (try these first)”sentience statussentience listsentience open --latestMost common issue
Section titled “Most common issue”Hook not firing → check PATH or restart Claude Code.
Install
Section titled “Install”pip install sentience-governor fails with externally-managed-environment
Section titled “pip install sentience-governor fails with externally-managed-environment”Modern macOS and Linux Pythons block pip install outside a virtualenv (PEP 668). Use pipx instead:
pipx install sentience-governorpipx install fails with ensurepip exit status 1
Section titled “pipx install fails with ensurepip exit status 1”pipx defaulted to a Python with a broken ensurepip. Force a known-good version:
PIPX_DEFAULT_PYTHON=python3.12 pipx install sentience-governorpipx is not installed
Section titled “pipx is not installed”brew install pipx # macOS# or:python3 -m pip install --user pipx # Linux / WSLpipx ensurepathRestart your shell after pipx ensurepath.
sentience: command not found after install
Section titled “sentience: command not found after install”Run pipx ensurepath, then restart your shell. The pipx bin directory needs to be on your $PATH.
Python version too old
Section titled “Python version too old”Sentience Governor requires Python 3.10 or newer. Confirm with python3 --version. If older, install a newer Python (brew install python@3.12).
Claude Code hook
Section titled “Claude Code hook”sentience status says hook is not firing
Section titled “sentience status says hook is not firing”Cause: One of: wrong settings file, CLI not on PATH, Claude Code started before you saved the config, or no tool calls happened in the session.
Fix:
- Confirm config location:
~/.claude/settings.json(user-global) or.claude/settings.json(project-local, takes precedence). - Confirm CLI resolves:
which sentience-claude-code-hookfrom Claude Code’s launch shell. - Restart Claude Code — it reads settings at startup.
- Make actual tool calls — the hook only fires on tool invocations.
/sentience-pulse does not appear in Claude Code
Section titled “/sentience-pulse does not appear in Claude Code”Cause: The skills directory was created after Claude Code started, or skills were not installed.
Fix:
- Run
sentience init claude-code(without--no-skills). - Restart Claude Code, then type
/sentience-help. - If you installed project-local skills with
--project, make sure Claude Code trusts that workspace.
/sentience-pulse says sentience: command not found
Section titled “/sentience-pulse says sentience: command not found”Cause:
The slash command shells out to the local sentience binary, but Claude Code cannot find it on $PATH.
Fix:
- Confirm
sentience --versionworks in a fresh terminal. - If you installed with pipx:
pipx ensurepath, restart your shell, then restart Claude Code. - Re-run
sentience init claude-code— it warns at install time ifsentienceis not resolvable.
/sentience-pulse reports no_signal in a running session
Section titled “/sentience-pulse reports no_signal in a running session”Cause: This is expected, not a failure. Per-turn token data is written when the Claude Code session ends — a still-running session has events but no turn/token records yet.
Fix:
End the session and run the pulse again (or run it against a previously ended session). Since v0.2.8.2, when the latest session has no token data the pulse shows your most recent session that does — with a transparent header naming it — so you don’t have to hunt for it (resuming a conversation mints a new session id, so the newest one is often an empty live segment). An explicit sentience pulse <id> is honoured exactly. If a session that has ended still reports no signal, run sentience init claude-code and start a new session.
sentience open --latest shows no events, but the hook fired
Section titled “sentience open --latest shows no events, but the hook fired”Cause:
The curated viewer is hiding baseline-noise events in --summary mode.
Fix:
sentience-cli ~/.sentience/traces/claude-code/<session-id>.jsonl# Or drop --summary:sentience open <id>Sync cloud telemetry
Section titled “Sync cloud telemetry”The experimental Sync cloud telemetry CLI was removed in v0.2.8.3. sentience-sync now prints a local-first notice and exits 0. Your local pulse, status, profile, and Claude Code capture are unaffected.
If you are trying to join the product update list, use the Sentience Sync email list on the website. That list is separate from the removed telemetry CLI.
Claude Code vs. library-integrated — which viewer?
Section titled “Claude Code vs. library-integrated — which viewer?”- Claude Code sessions →
sentience(curated). - MCP wrapper / LangChain callback →
sentience-cli(raw).
Still stuck?
Section titled “Still stuck?”Reach out via support on getsentience.ai.
Include:
- The exact CLI command that failed
- Full stderr output
- OS and Python version