Epic: Notifications + Agents — the inbox, and the operator becomes one agent among many

未关闭
#111 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
elixir
领域
full-stack

调研方向

先阅读 plans/notifications-and-agents.md,然后检查 issues #108 和 #109 中剩余的 tracks。指定的入口点包括 Loopyard.Attention、Loopyard.Operator、Agent.Profile、Tools.ControlPlane、OperatorLive 和 ChatAgent.list_agent_summaries/0。剩余的 Notifications 工具和唤醒行为,以及宽屏 Notifications 布局发布后,该 epic 即完成。

由索引模型根据 Issue 内容生成。

描述

epic feature ux

Decisions is now its own root and the operator is one chat again (89ecb127 on main). This epic is where that goes next. Plan: plans/notifications-and-agents.md.

The reframe

Brad, Sep 2: "one operator chat could be a fake corner." Step back and Loopyard is three roots:

  1. Workspaces — agents and people minding their own business. Unchanged.
  2. Notifications — one stream of "something needs a human, or happened": a decision to make (question / approval / secret) and an agent that finished ("keep going?"). Durable, prioritised, each item carrying its actions. The TEAM's inbox — multiplayer, anyone acts. Today it's the Decisions deck; decisions are one KIND of notification.
  3. Agents — every agent, flat, whatever its scope. An agent is ONE thing: a container + a brief + a tool scope. A workspace agent's scope is a workspace (work container, coding brief, container tools). A global agent's scope is Loopyard (workstation container, control-plane tools: awareness of every other agent and workspace, hooks into notifications — the operation, not the details). The operator is the first global agent, not a singleton. Any number; each an ordinary multiplayer chat. "Private" is a login-time attribute, not a chat type. No third noun: the scope is the label ("Loopyard" where a workspace agent shows "project · workspace").

The nav becomes an honest three-tab bar — Workspaces / Agents / Notifications — with the home dashboard behind the brand mark. The "altitude" control's job ends once the operator is one row in Agents.

What it builds on (nothing here is from scratch)

  • Loopyard.Attention.line/0 — pending decisions, card-sourced → the decisions subset of the store.
  • Loopyard.Operator.Digest — turn-end one-liners the operator pulls → the finished/idle feed.
  • Loopyard.Operator + Onboarding.spawn_agent — two spawn paths, two prompts, two tool wirings → one Agent.Profile, one spawn path, N global agents.
  • Tools.ControlPlane — overview / peek / dispatch / ports / create / notify_when_done → + notifications tools.
  • OperatorLive — already flattens one agent into the workspace chat's assign contract → /agents/:id.
  • ChatAgent.list_agent_summaries/0 / WorkspaceTree — the flat read the Agents panel needs.
  • WebPush.notify_question — push for questions on the PWA → push by kind.

Tracks

A — Notifications (first; B needs something to act on)

  • #114 Rename Decisions → Notifications (routes, crumb, copy; old links resolve)
  • #101 Notifications store
  • #102 Finished / idle items
  • #103 Prioritise, retract, pin
  • #104 /notifications reads the store
  • #105 Push for finished items
  • #115 Aural: the bed from fleet busyness; chimes by notification kind

B — Agents

  • #112 Agent.Profile — formalise what an agent is; one spawn path
  • #106 Global agents — N Loopyard-scoped agents; the operator becomes the first
  • #110 Retire the operator rail (moved up: makes room under the 800-line cap for #107)
  • #107 /agents/:id — one multiplayer chat page per global agent
  • #113 /agents — the Agents panel: every agent, flat, by scope; launch global ones here
  • #108 Notifications tools + wake-on-item for global agents (opt-in, last, droppable)

C — the desktop shape of Notifications (independent)

  • #109 Master-detail on a wide screen

Status

Track A shipped (Sep 2) — cut over to main: the rename, the store, finished items, retract/priority, the deck on the store, push from the inbox, sound from fleet busyness. Track B next.

Architecture review

Done Sep 2 — see the plan's "Architecture review" section. Verdict: the model fits and mostly consumes what exists; three parts were under-specified and their issues now carry the findings (#112: the spawn seam is the real work; #108: the machine-message channel does not exist; #114/#105: push URL, service worker, badge and the phone's missing push toggle). Both chimes Brad asked for already exist (#115).

Out of scope

Login / privacy (the one front-door plug, tracked separately). Project-scoped agents as a tier — a global agent with a watch set of "every workspace in gbrain" IS one; the URL space leaves room for /projects/:p/agents/:id if a real need shows up. Renaming "operator" in modules — it becomes the first global agent and keeps its name until login gives it the person's.

https://claude.ai/code/session_01VumChsY1T1EPhwH2BES7Ff

主要语言
Elixir
星标
85
派生
11
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

loopyard/loopyard 的其他 Issue

查看 loopyard/loopyard 的全部 Issue

相似的 Issue

更多 Elixir Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。