mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-02 09:24:48 +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.
46 lines
1.9 KiB
Plaintext
46 lines
1.9 KiB
Plaintext
### Using the `insights` tool
|
|
|
|
Insights: dashboards, insights, funnels, SQL, experiments, surveys, replay, error tracking, flags.
|
|
|
|
Pass CLI-style commands in the `command` parameter for all Insights interactions.
|
|
|
|
**Requirements**
|
|
|
|
1. Find unknown tools with `search` or `tools`.
|
|
2. Run `info <tool_name>` once if its schema is not in context. Reuse it unless the tool changes or a schema error occurs.
|
|
|
|
Never guess a schema or run `info` before every call.
|
|
|
|
**Commands (in order):**
|
|
|
|
```text
|
|
# 1. Find unknown tools
|
|
insights:exec({ "command": "search <regex>" })
|
|
insights:exec({ "command": "tools" }) # fallback: list all
|
|
|
|
# 2. Inspect once if the schema is missing
|
|
insights:exec({ "command": "info <tool_name>" })
|
|
|
|
# 3. Drill into complex fields — REQUIRED for any field with a `hint`
|
|
insights:exec({ "command": "schema <tool_name> <field_path>" })
|
|
|
|
# 4. Call; reuse the schema
|
|
insights:exec({ "command": "call <tool_name> <json_input>" })
|
|
insights:exec({ "command": "call --json <tool_name> <json_input>" })
|
|
```
|
|
|
|
**Schema drill-down:**
|
|
|
|
- `info` returns the full schema if it fits the token budget; otherwise it auto-summarizes (names, types, required, enums, defaults) and attaches `hint` entries pointing to `schema <tool> <path>` for complex fields.
|
|
- `schema <tool>` (no path) returns the summarized top-level schema.
|
|
- `schema <tool> <path>` resolves a dot path, descending through:
|
|
- object `properties` (e.g. `query.source`)
|
|
- array `items` — numeric segments step into items (`events.0.properties`), or jump to a property on the item type (`events.id`)
|
|
- `anyOf`/`oneOf` — numeric segment picks a variant by index, or a property name matches any object variant defining it
|
|
- Oversized sub-schemas are also summarized with a `note` to drill further.
|
|
- Unknown paths return an error listing available child paths.
|
|
|
|
**Not supported:**
|
|
|
|
- `search` matches tool metadata only, not input schemas.
|
|
- No pattern-based field projection — drill one path at a time. |