docs: accept Herdr bindings and keep Niri workspaces flexible

This commit is contained in:
kiri committed 2026-09-09 21:07:04 +02:00
1 parent a2486c93c5
commit 7cbae3d221
2 files changed
+12 -11

No files matched your search

+6 -4
View File
@@ -36,13 +36,15 @@ use a flake to declare its tools without Nix owning the surrounding workspace.
do not fit as naturally. Accessible mail for tools and agents matters separately
from choosing a mail reader. Preserve meaning and source context, not just text.
- Herdr is the chosen agent workspace manager: its spaces, running-agent overview
and attention states fit. Adapt its keybindings to the keyboard-driven setup.
and attention states fit. Its configured keybindings are accepted in daily use.
Use Ctrl+Alt for direct Herdr actions alongside Super for Niri and Ctrl navigation
in Neovim; retain Herdr's prefix bindings. Agent-deck's startup issues and other
session-manager alternatives are not the current focus.
- Current friction is a lack of consistent project and agent working practices,
including Niri workspace use. Tool choice and agent collaboration need to be
considered together. Alignment, maintainability and human attention matter
- Keep Niri workspaces flexible. Herdr supplies enough structure that no strict
desktop grouping, fixed workspace names or project-to-workspace mapping is
needed now. Let actual use inform any later organization.
- Project and agent working practices remain exploratory.
Alignment, maintainability and human attention matter
alongside speed/cost. Agent-workflow evaluation is deferred; no fixed delegation
pattern has been selected.
- Repositories should contain code and documentation needed by that code, not