hctl
humanctl

An attention router for a scarce human · humanctl

1 active asks · 1 waiting · 2 attached

SiteGitHub
Need your answer1 waiting2 attached

Lock the chief-of-staff MVP loop

What should the first implementation optimize for?

Decide what the first implementation should optimize for before adding stronger channels or presence inputs.

Why now
The next refactor will either harden the unblock loop or drift into nicer artifact browsing without better interrupt-and-resume behavior.
If ignored
The app will keep mixing queue, canvas, and interrupt behavior without a clear priority.

Reply here

Choose a steer or write back.

Writes back into `.humanctl`.
ContextAttention router overviewWorking canvas

What I’m showing you

Working canvas

Keep HTML dashboards, previews, and comparisons organized, pinnable, and easy to reopen.

comparisoncanvasartifactshtml

Working canvas

Keep the useful HTML around.

Agents should still be able to show dashboards, previews, comparison boards, and little local tools. The difference is that humanctl should organize them instead of leaving them scattered across threads and temp files.

  • Artifacts should be labeled, pinnable, and grouped by the run or ask that created them.
  • Important views should be reopenable later without replaying the conversation.
  • The canvas is artifact memory, not the thesis of the product.
Other asks can wait
What do you think of this humanctl loop?
1 background watches
Presence-aware routing