mirror of
https://github.com/Kaelio/ktx.git
synced 2026-06-25 08:48:08 +02:00
feat(cli): guide next action at end of ktx setup, not reruns (#256)
Re-running setup was the dominant action for installs that completed setup but never ingested. Classify completion (incomplete | needs-context | needs-agents | ready) and drive one obvious next action per state: route a config-complete project straight to the build, point unbuilt-context users at `ktx ingest` instead of re-running setup or dropping to a bare shell, and confirm readiness for fully-set-up projects rather than reopening the edit menu.
This commit is contained in:
parent
cb6a67c2d7
commit
45aa95d2cc
8 changed files with 360 additions and 59 deletions
|
|
@ -215,8 +215,8 @@ The wizard walks you through everything **ktx** needs in one pass:
|
|||
SQLite, PostgreSQL, MySQL, SQL Server, BigQuery, and Snowflake.
|
||||
5. **Context sources** - optionally adds dbt, MetricFlow, LookML, Looker,
|
||||
Metabase, or Notion. You can skip and add them later.
|
||||
6. **Build** - runs the first ingest so semantic sources and wiki pages
|
||||
are ready for agents.
|
||||
6. **Build** - offers to run the first ingest so semantic sources and wiki
|
||||
pages are ready for agents. If you skip it, build later with `ktx ingest`.
|
||||
7. **Agent integration** - installs project-local rules for Claude Code,
|
||||
Codex, Cursor, OpenCode, or universal `.agents`.
|
||||
|
||||
|
|
@ -247,6 +247,18 @@ progress under `.ktx/setup/` and resumes from the remaining work.
|
|||
> resuming setup, connecting an agent, checking status, or exploring a
|
||||
> pre-built demo project.
|
||||
|
||||
When the wizard finishes, it states where you stand and the single next action:
|
||||
|
||||
- **Context built** - **ktx** confirms it is ready for agents and points you to
|
||||
open your coding agent and ask a data question.
|
||||
- **Build skipped** - **ktx** tells you setup is complete and that the only step
|
||||
left is to build context with `ktx ingest`.
|
||||
|
||||
Re-running `ktx setup` on an already-configured project goes straight to the
|
||||
remaining step - building context or connecting an agent - instead of
|
||||
re-asking every question. Once everything is ready, it confirms you are set
|
||||
rather than reopening the configuration menu.
|
||||
|
||||
## Verify
|
||||
|
||||
When setup finishes, check readiness:
|
||||
|
|
@ -268,6 +280,9 @@ Agent integration ready: yes (codex:project)
|
|||
|
||||
For a structured check inside scripts, use `ktx status --json`.
|
||||
|
||||
If you skipped the build, `ktx context built` shows `no`. Build it with
|
||||
`ktx ingest` - there is no need to re-run `ktx setup`.
|
||||
|
||||
When setup finishes building context, its final context check looks like:
|
||||
|
||||
```text
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue