mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-03 00:52:32 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
1.8 KiB
1.8 KiB
name, description
| name | description |
|---|---|
| insightscli | Insights developer CLI and repo tooling reference. Use when the user mentions insightscli, asks about repo CLI tools, bin scripts, Makefiles, how to run/build/test/lint, or any dev environment commands. |
insightscli - Insights Developer CLI
Unified CLI for Insights development. Wraps all repo scripts, bin commands, and tooling behind a single entry point. There is no Makefile — insightscli is the equivalent.
Run insightscli --help to get the full, current command list. Run insightscli <command> --help for any subcommand.
Process logging (for agents/debugging)
Where logs land depends on how the stack was launched:
Detached (insightscli up -d) — phrocs writes files under .insights/.generated/logs/ on every boot:
phrocs.log— the daemon's own stdio; the place to look when phrocs died at startup and the phrocs MCP tools are unreachable.<process>.log— per-process output (truncated on each start), where<process>matches the phrocs process key (seebin/mprocs.yaml).insightscli doctor:reportprints thephrocs.logpath and tails its last lines.
TUI with insightscli dev:setup --log, then insightscli start — adds a tee wrap per process:
/tmp/insights-<process>.log— full stdout+stderr; persists in the generated config untildev:setupis re-run without--log.
When the phrocs MCP is reachable, prefer mcp__phrocs__get_process_logs over grepping files.
Key references
insightscli.yaml— command definitions (source of truth)tools/insightscli-commands/insightscli_commands/— Insights-specific lazy Click command modulestools/insightscli/README.md— framework documentationtools/insightscli-commands/README.md— Insights commands documentation