Problem
On a fresh kanon init, running kanon import prints warnings and a synthesized kanon.yaml, but it does not tell the user which agent files were discovered or where the imported content came from. In the first-run case I tested, the output included warnings and YAML only, with no discovery summary or source-path header.
That makes the import result hard to trust: a new user cannot easily tell whether the data came from Codex, Claude, or project files, or whether the command found anything meaningful before it started emitting warnings.
Repro
./bin/kanon --home "$HOME/.config/kanon" init
./bin/kanon --home "$HOME/.config/kanon" import
Suggested fix
Add a short summary before the YAML preview that names the discovered source files/units and counts what will be imported, for example:
- instructions from
~/.codex/AGENTS.md
- skills from
~/.claude/skills/...
- MCP servers / hooks from their source files
Even a compact header would make the preview much easier to understand on first run.
Problem
On a fresh
kanon init, runningkanon importprints warnings and a synthesizedkanon.yaml, but it does not tell the user which agent files were discovered or where the imported content came from. In the first-run case I tested, the output included warnings and YAML only, with no discovery summary or source-path header.That makes the import result hard to trust: a new user cannot easily tell whether the data came from Codex, Claude, or project files, or whether the command found anything meaningful before it started emitting warnings.
Repro
Suggested fix
Add a short summary before the YAML preview that names the discovered source files/units and counts what will be imported, for example:
~/.codex/AGENTS.md~/.claude/skills/...Even a compact header would make the preview much easier to understand on first run.