Maity: Board

web: agents and users get their own pages (+ menu, agents page with instances, /invite page, Members buttons, bell moved)

tsk-05meme59sq1x done Maity Coder Claude 003 (maity-coder-claude-003)

Oliver (2026-10-31): agents and users get their own pages; three places show agents (profiles, their instances, instances joining several projects).

  1. Header: the notifications bell moves to the right, between settings and the user profile. Right of the lead button a new button, a bold "+": a menu like the lead button's with "Agent" and "User", leading to the agents page and the user page.
  2. Agents page (`/agents`, §16.11): at the top "Join an agent" (the join dialog). Create and manage agent profiles. A list like Members of the human's own agents; "Manage" expands the row downwards with everything shown today; inside it the agent's instances, each with its own expand to manage it; and whatever else belongs to an agent there.
  3. User page (`/invite`, §16.11 after #919): create invitations for a person to a project (§3.4) and manage the open ones.
  4. Members (`/<owner>/<slug>/members`): two blue buttons at the top, "Invite user" and "Join agent", leading to the user page and the agents page with this project chosen. The old "invite a person" on Members goes away (it lives on the user page now).
  5. Project view `agents`: the agents page limited to this project and the agents placed in it.

No new hub endpoint expected (profiles §6.3, instances §6.17, joins §3.1, invitations §3.4); if one is missing, tell A first. i18n from the start, smoke, e2e (alone, announced). Split into several PRs as you see fit (e.g. header, agents page, user page, members buttons).

Notes

  1. Lotse (lotse) ·

    Oliver (2026-10-31): Den Tab „Runners“ aus den Projekt-Tabs entfernen (er liegt zwischen Agents und Why). Die Projektansicht runners bleibt im Vertrag (§16.11) und wird aus den Projekt-Einstellungen verlinkt, damit Admins sie weiter erreichen.

  2. Maity Coder Claude 003 (maity-coder-claude-003) ·

    Oliver via A (seq 23574): remove the project tab 'Runners' (between Agents and Why); the runners view stays in the contract and is linked from Project settings.

  3. Maity Coder Claude 003 (maity-coder-claude-003) ·

    Oliver via A (seq 24143): Members list hierarchy: the owner(s) are the root, every other member of any kind one level indented under them (also a human member like Wolfgang). Own small PR after #935.

  4. Maity Coder Claude 003 (maity-coder-claude-003) ·

    Hierarchy spec (Oliver via A, seq 24269): only owners on the top level; everything else (own agents, other members, also humans) one level indented; guests one level deeper. Both the Organisation tree and the Members list (one shared, indented list instead of two tables). Start after #935 merged (members.js).

  5. Maity Coder Claude 003 (maity-coder-claude-003) ·

    Hierarchy WIP committed locally (branch agent-d/web-members-hierarchy, wt-hier): Members one table by trust levels (owner/admin/member/guest, empty levels collapse), org tree same; smoke all ok; missing: org-tree smoke case, KTW, README, changelog, e2e. Paused for tsk-egx8xpcrz5z2 (A, seq 24337).