Feature Request: Configurable office sizes (small, medium, large) for hardware optimization
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
The issue describes the 3D office layout and setup UI, but names no files, tests, or entry points. Start by locating where office desk islands are created and how the setup UI stores configuration; then determine how the selected footprint should affect agent capacity and rendering. Done means users can choose small, medium, or large, with large remaining the default.
Written by the indexing model from the issue text.
Description
feature Request:
Currently, the 3D office has a fixed-size layout (4 desk islands) alongside its 3 visual themes (office, medieval, Star Wars). However, for users working on smaller projects or self-hosting on lower-end PCs/servers, rendering and managing a large office is unnecessary and consumes extra CPU/RAM. If a user only needs to deploy 1 to 4 agents, having the full-sized room loaded creates an avoidable performance bottleneck.
Solution:
It would be highly beneficial to add an option (e.g., in the setup UI) to choose the office footprint:
- Small: 1 desk island (capacity: 1 to 4 agents) -> Perfect for low-power PCs and lightweight projects.
- Medium: 2 desk islands (capacity: up to 8 agents) -> A balanced workspace.
- Large: 4 desk islands (capacity: up to 16 agents) -> The current default full-scale layout.
Drawbacks considered:
- Users can currently just ignore the extra desks, but this doesn't solve the hardware overhead for those hosting the 3D environment on restricted machines.
- The 2D version strips away the very essence of the virtual office concept, which allows users to interact with agents just like in a real office.
Additional context
Adding this feature would bring a great sense of personalization and adaptability. It would ensure agent-office scales down gracefully for users with hardware constraints, allowing them to adapt the space strictly to their own needs without compromising performance. Since "Large" would remain the default, this wouldn't disrupt the existing workflow for current users.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 11
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 161
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AgentSystemLabs/agent-office
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AgentSystemLabs/agent-office#297 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
AgentSystemLabs/agent-office#319 ·
Maintainers usually reply within 1 day
-
Not a cat option???Open
Difficulty 3/5 Half a day Newbie friendliness 45/100
AgentSystemLabs/agent-office#314 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
AgentSystemLabs/agent-office#303 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
AgentSystemLabs/agent-office#302 ·
Maintainers usually reply within 1 day
All issues in AgentSystemLabs/agent-office
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stellar/stellar-dev-skill#151 ·
Maintainers usually reply within 1 day
-
area:arcade game ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
fderuiter/deruiter.dev#2281 · 1 comment ·
Maintainers usually reply within 1 day
-
scope: data grid type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
fix(frontend): correct VITE_IS_DEVELPOMENT typo in shared/app.ts and align dev environment flagsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
vicharanashala/ajrasakha#1439 ·
Maintainers usually reply within 1 day
-
Add: TV5Monde AsieOpenapproved check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day