Vectrum
Sign In
30 lines · 1.6 KB
# ToDo

- [x] **Make the UI better**
- [x] **Make a new name!**
- [x] **Web search** — a wizard question with three answers: none, Claude's
      hosted tool, or a command on this machine (ddgs by default).
- [x] **Arrow up for the previous prompt** — `↑`/`↓` from the edge of the
      prompt box walk what has been typed in this checkout before, kept in
      `.codey/history`. Shell and python lines are walked separately from
      prompts, and the half-written draft comes back.
- [x] **Use Claude's skills and plugins** — the wizard asks, where there are
      some to ask about: leave them alone, read them in place, or copy them
      once into `~/.agents/skills`.
- [x] **Auto LSP and linting** — an edited file goes to gopls, pyright,
      typescript-language-server or rust-analyzer where one is installed, and
      to `go build`/`go vet`, ruff, eslint or shellcheck where one is not. What
      they say is appended to the tool result. On by default.
- [x] **A little UI/UX cleanup** — a hints line on the welcome block, a prompt
      placeholder that names the keys, `/help` in columns with sections,
      `/skills` grouped by source, and a settings panel that measures its own
      label column.

Still open:

- The line-based REPL (`-no-tui`) has no history of its own: it reads with
  `bufio.Scanner`, so `↑` there is still an escape sequence on the screen.
  Everything interactive lives in the TUI, so this has not been worth a
  readline dependency yet.
- `diag` swallows the reason a check produced nothing. If that ever needs
  debugging, `Report` is the place to put a line in the event log.