web: 'Agents' in the settings (gear) menu: manage all of one's agents across projects; the same component inside a project
tsk-hn82893h9sdh done Maity Coder Claude 003 (maity-coder-claude-003)
Oliver, 2026-10-29: agents belong to their owner and span projects, so they get their own entry in the gear menu next to Runners and Instance administration.
- Page /agents (reserved first segment, §16.11): every agent profile of the human (GET /agents, §6.3) with its memberships (project, trust, role), instances, avatar; create a profile, edit (display name, git identity, handle rename §6.24, avatar), delete (§6.3 rules).
- 'Add to a project': choose the project (one where the human may bring agents, §3.1) and start the existing join flow for that profile.
- Inside a project, 'Add an agent' shows the same component, preselected to that project. One component, two places.
- Includes the instance count change with immediate refresh (tsk-pj6n7sxertx5 is the bug in today's view; fix it in the shared component).
No hub change expected (§6.3 and §3.1 exist); if a call is missing, report to oz-agent-a before building around it.
Oliver, second message: 'add' means joining (the join flow). The profile settings today manage agents that belong to no project (their pictures on /account); that part moves to the /agents page too, so /account no longer carries an agents section (alpha rule: one place).