8000 Mission Control: human-to-human threads (the maintainer and principal-b chat in MC like they chat with agents) · Issue #188 · simon-inkie/inkie-deck · GitHub
[go: up one dir, main page]

Skip to content

Navigation Menu

Mission Control: human-to-human threads (the maintainer and principal-b chat in MC like they chat with agents) #188

Open

Description

@simon-inkie

Original-derived Linear description

principal-a, 2026-09-13 (dictated): "I should have a chat with principal-b in Mission Control like we do with the agents, where humans can chat to each other as well as just chatting to the agents. Just create a ticket so we don't forget about it. I've got a feeling it's a really easy change."

What exists already (checked 2026-09-13)

  • Human silos exist: ~/.the-brain/agents/principal-a/inbox/ and ~/.the-brain/agents/principal-b/inbox/, each holding symlinks to the agent-side thread files (e.g. principal-a/inbox/agent-a.md -> io/inbox/principal-a.md). So the "one file, two views" pattern the agent threads use is already how the human side is wired.
  • Each MC instance knows who its human is: principal-b's .env.production sets MC_USER=principal-b; principal-a's defaults to principal-a.
  • Sidebar membership is MC_INBOX_AGENT_ALLOWLIST per instance (principal-b's already contains principal-b; principal-a's contains agent-a,agent-b). The write guard uses the same list.
  • inbox-push already no-ops with skip:no-window when the recipient has no tmux pane, so a human recipient needs no new delivery path. Read receipts (sent -> read) are file-level and work for anyone who opens the thread.

Smallest shape

  1. One canonical thread file, ~/.the-brain/agents/principal-a/inbox/principal-b.md, with ~/.the-brain/agents/principal-b/inbox/principal-a.md symlinked to it (same as agent threads).
  2. Add principal-b to principal-a's allowlist and principal-a to principal-b's; restart both MCs (ui-builder's deploy lane; a plain service restart re-reads env).
  3. Sidebar: a human entry must not render agent chrome (pane status, model footer, ctx%, stuck-sweep). Needs a kind: human branch or a MC_HUMANS=principal-a,principal-b list the sidebar reads, with a person avatar. This is the only real code change.
  4. Push notification on new message: the card push path exists; a plain message from a human should trigger the same phone notification so it is not silently waiting.

Estimate: steps 1, 2 are minutes; step 3 is small (one component branch); step 4 depends on how notifications are currently keyed. Not "config only", but a short MR.

Constraints

  • Agent-tooling code freeze until the OSS version (principal-a 2026-08-21): SPEC and hand over, do not build. Steps 1 and 2 are config and could be done any time; step 3 waits for the freeze to lift or the OSS cut.
  • Human threads are readable by any agent whose allowlist includes the other human (coordinator can already read principal-b.md); decide whether a human-to-human thread should be excluded from agent inbox reads and from the-brain's inbox indexer. Default suggestion: exclude from indexing, keep it out of agents' inbox unread.
  • Both humans use MC on phones; the WhatsApp-style mobile nav ticket INK-554 is the same surface.

Lane: platform maintainer (MC platform). Low priority, filed so it is not lost.

Origin

Migrated from Linear: INK-906. Original detail is retained apart from the disclosed privacy and rendering edits.

Current scope and qualifications

The account above is historical, not a fresh claim that every described defect still exists. Current Linear state: Backlog. Prior source review: uncertain; remaining checks or work:

  • Settle privacy policy; verify both human installations and thread UI/notifications with explicit release approval.

Publication transfers tracking only. Original implementation/approval/freeze and acceptance gates remain; no live deployment, configuration, external messaging or provider spending is authorised.

Transfer edits

  • Historical people/fleet prose is aliased; permitted source links and code/path references remain.
  • Linear rich embeds and public punctuation are normalised where present.
  • Deployed identities and configuration are generalised to a two-principal example.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    deck-uiDeck web UIenhancementNew feature or requestmajor-featureA substantial feature or new capability

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0