Skip to content

Add office fleet visibility and state mapping#110

Draft
iamlukethedev wants to merge 3 commits into
mainfrom
cursor/multi-agent-config-state-4e1b
Draft

Add office fleet visibility and state mapping#110
iamlukethedev wants to merge 3 commits into
mainfrom
cursor/multi-agent-config-state-4e1b

Conversation

@iamlukethedev
Copy link
Copy Markdown
Owner

@iamlukethedev iamlukethedev commented Apr 9, 2026

Summary

  • add a configurable office agent state mapping preference for local and remote presence
  • show a stronger fleet visibility HUD in the office with local vs remote counts and highlighted active/error agents
  • capture remaining discussion Real-world multi-agent fleet feedback — 9 agents in production #8 ideas in a backlog markdown file
  • fix the office state mapping callback typing so production builds pass

Testing

  • npm run test -- --run tests/unit/officeAgentStateMapping.test.ts tests/unit/studioSettings.test.ts tests/unit/officeEventTriggers.test.ts
  • npm run build
  • npm run smoke:dev-server
  • npm run lint (known pre-existing repo errors remain in AgentBrainPanel.tsx and useOnboardingState.ts)
  • manual office walkthrough with demo backend and state-mapping interaction

Artifacts

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

cursoragent and others added 3 commits April 9, 2026 14:36
Co-authored-by: Luke The Dev <iamlukethedev@users.noreply.github.com>
Co-authored-by: Luke The Dev <iamlukethedev@users.noreply.github.com>
Co-authored-by: Luke The Dev <iamlukethedev@users.noreply.github.com>
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.

2 participants