# Agent workers in a pastel office > A stylized 3D office presents software agents as desk-based coworkers, with status labels, terminal panels and task boards for managing GitHub issues and pull requests. - Kind: Video - Page: https://meetreference.com/v/video-agent-workers-in-a-pastel-office-af2005/ - Ready-to-use agent handoff: https://meetreference.com/v/video-agent-workers-in-a-pastel-office-af2005/agent.txt - Authorship: AI-made, per the source - Made with: Not stated - Model: Opus 5.5 - Built with: not stated - Services: GitHub - Style: Product launches; low-poly, pastel, playful, spatial-interface, game-like, rounded-ui - Length and format: 42 sec, 1106:720 (1106x720 source) - Playback: a muted visual reference. The original soundtrack is available only at the source. - Shared by @webdevcody in X, Sep 26, 2026: https://x.com/webdevcody/status/2103653857377292720 - Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference. ## Before you start Guidance from Reference, separate from the creator's instructions. 1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present. 2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized. 3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed. 4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting. 5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use. ## Recreating this video This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work. Adapt a technical workflow into a small low-poly workplace, assigning each worker or task a recognizable character and location. Use pastel rugs and furniture clusters to distinguish work areas, with short name badges and clear status labels. Reserve detailed information for consistent overlay panels and make wall boards correspond to real workflow stages. 1. Open the live work or source and inspect the frame images below. 2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand. 3. Compare the result against the reference. Use your own assets and credit the original creator. ## What it looks like Written by Reference from the video frames, not by the creator. A playful 3D virtual office with small cartoon agents, desks, computers, plants, and colorful task-management screens. - Color: Warm cream and honey-colored floors, muted tan walls, bright blue and green accents, purple rugs and panels, and dark navy interface elements. - Type: Compact sans-serif labels and buttons in rounded white or gray interface panels; small task cards use simple, high-contrast headings. - Framing: The office scenes center on desks and agents against open floor areas, while interface panels and dialogs sit near the edges or overlay the workspace. Other screens show kanban-style boards with columns and task cards. - Structure: A persistent top navigation and right-side worker/status panel frame the office view. Task details appear in centered modal dialogs; GitHub work is organized into board columns with labeled cards. Storyboard, nine frames spread across the video: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/storyboard.webp - Frame 1 at 2.3s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f1.webp - Frame 2 at 6.9s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f2.webp - Frame 3 at 11.5s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f3.webp - Frame 4 at 16.1s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f4.webp - Frame 5 at 20.8s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f5.webp - Frame 6 at 25.4s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f6.webp - Frame 7 at 30.0s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f7.webp - Frame 8 at 34.6s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f8.webp - Frame 9 at 39.2s: https://meetreference.com/media/video-agent-workers-in-a-pastel-office-af2005/f9.webp ## Links - Watch: https://x.com/webdevcody/status/2103653857377292720 - Original post: https://x.com/webdevcody/status/2103653857377292720 - Discovery collection: https://data.openchamber.dev/opus-5-5-videos/v/webdevcody-2103653857377292720