CodeLayer navigation inspo

[GappelSolutions]

Hey guys,

I saw that you're already at 100 issues after the video... but thought I'll still try to give a bit of an input.
For the past month, I've been using CodeLayer/HumanLayer Nightly and it's been the best experience ever, workflow wise.
I will migrate to t3 code as the repo feels more and more inactive. You're locked into Claude, in the current nightly the scrolling is buggy and it's missing attachments, project presets and grouping.
Still, I really encourage you to look into it for a few minutes. There are 3 differentiators, that i got from no other project:

1. Keyboard first:

• They have a vim like structure with normal and insert
• You can open a create dialog (C) with chat title, project and prompt
• You can archive the whole chat (E)
• You can toggle views (T) (minimap, todo, none)
• You can navigate to parent (ESC)
  • Parent is a hub like chat overview which you could implement with simple navigation (J/K + ENTER) and (L/H) for next/previous project
• You can enter insert (ENTER) focusing the chat prompt on the current screen and go back to normal (ESC)
• Enter doesn't send a message, CMD + ENTER does (this one's super refreshing)
• Minimap navigation:
  • Every agent step is one point on the map
  • Chat is scrolled using vim Up (K), down (J), first (GG), latest (SHIFT + G)

2. Transparency

• Every chat, toolcall, thinking process, ... is expandable instead of the narrow view of claude or codex
• You can check the raw json calls to trace agent behavior
• it gives you one liners are compressive thinking summaries instead of the usual all or nothing approach of all others

3. Human in the loop focus

• Workflow: Research, Review, Plan, Review, Iterate, Review, Implement, Review, Commit, Review
• Each step is optional
• Focus is on context engineering
• New Session for everything
• Research done? New session with research file; Plan done? new session with plan file...
• You probably won't apply this as you don't build agent or manipulate them but it decreases token usage and increases quality by a big chunk
• When migrating, I'll just reuse the workflow skills, leave the agent optimizations behind and integrate new session chaining skills

Would be nice if you could implement the "keyboard first" as optional at least. I experienced, that it's a complete game changer as you are jumping between project every half minute. Same for archiving. Keep everything lean and efficient.

Thanks for your work!

[juliusmarminge]

This is an inspiration dump rather than a scoped problem with acceptance criteria, and the navigation UI has changed substantially since it was filed. Specific CodeLayer-derived ideas can be proposed individually.

This was closed as part of a large repo-wide maintenance sweep. If you think it's still relevant, please reopen.