Skip to content

feat: add dynamic Office mode for agent families - #75

Open
Adayhg wants to merge 26 commits into
patoles:mainfrom
Adayhg:codex/office-mode-mvp
Open

Adayhg wants to merge 26 commits into
patoles:mainfrom
Adayhg:codex/office-mode-mvp

Conversation

@Adayhg

@Adayhg Adayhg commented Sep 5, 2026

Copy link
Copy Markdown

Summary

  • Add a dynamic Office view with Sims-like avatars, rooms, states, and a reversible Graph switch.
  • Discover new Codex agents from live rollout families, preserve root-to-child and nested relationships, and use stable opaque IDs with fail-closed handling for unknown or ambiguous targets.
  • Keep Office projection sanitized; telemetry is opt-in and local services bind to localhost.

Validation

  • npm test: 83 passed, 0 failed (root 33, web 10, extension 40).
  • TypeScript checks passed for web, extension production, and extension tests.
  • Next production build, Vite webview build, and extension build passed.
  • Live canary observed one family with a root placeholder, two direct children, and one nested grandchild; 4 agent_spawn events were grouped into one session.
  • Rollout files remained unchanged while watched; UI and relay listened only on 127.0.0.1.

Follow-up activation gates

  • Run the full 30-minute canary, measure end-to-end discovery latency, and verify atomic rename/replacement rotation before treating this MVP as production-activated.

@cla-assistant

cla-assistant Bot commented Sep 5, 2026

Copy link
Copy Markdown

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Aday seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@Adayhg

Adayhg commented Sep 6, 2026

Copy link
Copy Markdown
Author

Follow-up: work-based agent names

Agents now receive a fixed-vocabulary Spanish role label inferred from bounded work hints:
Orquestador, Seguridad, Validador, Investigador, Implementador, Documentador, Diseñador,
Integrador, Analista, or Especialista. Terra/Luna are shown as a secondary model-family
marker (for example, Seguridad · Terra). The original prompt/task text is never copied
into the label, and the opaque ID remains available for exact identification.

Validation after this follow-up: 86 tests passed; TypeScript, Next, webview, and extension
builds passed.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant