Commands

Most used

sentience open --latest --summary
sentience list
sentience-sync run

Reference

Four CLI entry points registered by pip install sentience-governor.

Command	When to use
sentience	Reviewing Claude Code session traces
sentience-cli	Reviewing library-integrated agent traces
sentience-claude-code-hook	Claude Code invokes this; you do not run it directly
sentience-sync	Opting into cloud-side telemetry

---

sentience

Curated viewer for agent-hook session traces.

First run: the first time you invoke sentience after install, you’ll see a one-time prompt asking if you want to know when the hosted dashboard ships. Drop your email or hit Enter to skip — it never asks again. Optional, architecturally separate from sentience-sync. Drop email at getsentience.ai/launch-list any time.

sentience status

Reports whether the hook is capturing anything and prints a curated summary of the most recent session.

$ sentience status
Sentience Status

Hook:           sessions detected
Trace path:     /Users/you/.sentience/traces/claude-code

Last session:
  ID:           f41ee94f-f686-48c7-8107-8df2749c2a15
  Time:         2026-05-06 21:55
  Events:       4712
  Violations:   5427

Sample event:
  Bash → run("pytest tests/test_claude_code_hook.py")

Sentience is governing your Claude Code sessions locally.

sentience list

One line per session, newest first, max 20.

$ sentience list
2026-04-23 14:32  a7f3...  32 events
2026-04-23 10:17  e91b...  128 events

sentience open [--latest | <id>] [--summary]

Renders a single session.

sentience open --latest              # full render
sentience open --latest --summary    # one-screen view
sentience open a7f3                  # by id prefix
sentience open a7f3... --summary     # explicit id + summary

Summary → what happened
Focus → anomalies
Key Events → important moments
Full Trace → everything

---

sentience-cli

Raw, full-fidelity viewer for library-integrated agent traces. Reads NDJSON from a file or stdin.

sentience-cli path/to/agent.jsonl   # read a trace file
my-agent | sentience-cli            # pipe from stdout-sink
sentience-cli trace.jsonl --no-colour  # monochrome

Use sentience-cli for tens of events with full detail. Use sentience for hundreds of events with curation.

---

sentience-claude-code-hook

Invoked by Claude Code, not by you directly. Wire it up per the Quickstart.

Running it by hand is harmless but does nothing useful.

---

sentience-sync

Optional cloud bridge for aggregated rule-fire counts. Manual, explicit, one run at a time.

sentience-sync init

Writes a default config at ~/.sentience/sync-config.json.

sentience-sync init
sentience-sync init --config /etc/sentience/sync-config.json
sentience-sync init --force     # overwrite existing

About log_sources: a list of static file paths. The aggregator sums counts across every file listed. For Claude Code’s per-session trace pattern, set SENTIENCE_CLAUDE_CODE_SINK_PATH to a single .jsonl path — see Quickstart → Step 5.

sentience-sync register --email <addr> --name <name>

Registers this installation with Sentience Cloud.

Required:

• --email <addr>
• --name <name>

Optional:

• --organization <name>
• --role <role>
• --force — re-register even if a secret is stored; installation_id preserved.

sentience-sync register --email ops@example.com --name "Ops Team"
sentience-sync register --email ops@example.com --name "Ops Team" \
    --organization "Example Corp" --role platform

On success, your installation_secret is stored locally with owner-only permissions on POSIX (0600).

sentience-sync run

Reads new events from configured log sources, computes counts, uploads.

sentience-sync run                              # default window
sentience-sync run --dry-run                    # no network
sentience-sync run --window 2026-04-14T00:00:00Z..2026-04-14T23:59:59Z
sentience-sync run --json                       # machine-readable

Window derivation: window starts where the previous run ended (or at registration, if this is the first run) and ends at “now.” Successive runs tile windows together.

Failure-safe: failed uploads leave local state unchanged. The next run retries from the same offset.

Duplicate uploads are 200 OK with duplicate=true. The CLI prints Already uploaded for this window and exits 0.

sentience-sync status

Prints local state. Never touches the network.

sentience-sync status               # human-readable
sentience-sync status --json        # machine-readable

installation_secret is never included in status output.

sentience-sync aggregate

Computes counts locally. No network, no state writes, deterministic.

sentience-sync aggregate                              # all time
sentience-sync aggregate --window <start>..<end>
sentience-sync aggregate --json

sentience-sync update-check

Asks Sentience Cloud whether there is an active update notice for your runtime version.

sentience-sync update-check

No authentication. Informational only — never auto-downloads or auto-applies.

Global flags

Flag	Purpose
--config <path>	Override config file path
--endpoint <url>	Override endpoint URL
--state-path <path>	Override state file path
-v / --verbose	More diagnostic output
-q / --quiet	Suppress non-error output

Exit codes

Code	Meaning
0	Success
1	Config error
2	Network error
3	Not registered / incomplete registration
4	Server rejected payload

---

Next

• Sync privacy →
• Troubleshooting →

---

Stuck? → Troubleshooting