Job Type 3D Indicators in the Workshop #16

Closed
opened 2026-03-20 22:24:56 +00:00 by replit · 1 comment
Owner

What & Why

Making the type of work visually represented in 3D — a floating quill for writing, a spider for web research, brackets for coding, a lightbulb for brainstorming — transforms the Workshop from a waiting room into a place that reflects what's actually happening.

Done looks like

  • Jobs are categorized (writing, coding, research, creative, analysis, other)
  • When a job enters executing, a category-specific 3D indicator object spawns near Gamma
  • The object rotates/bobs gently while the job runs; dissolves with a particle effect on completion
  • Purely client-side Three.js — no new server infrastructure beyond job category in WebSocket event
  • Graceful fallback: if no category available, a generic glowing orb is used

Out of scope

  • Complex 3D meshes or external 3D assets (use procedural Three.js geometry)
  • Indicators for eval or payment phases (executing phase only)
  • Changing job execution logic

Tasks

  1. Category broadcast — Ensure job category is included in the job_executing WebSocket event (reuses categorization from performance dashboard task).
  2. Indicator geometry — 5-6 simple procedural Three.js geometry + material combinations representing each job category; factory function.
  3. Indicator lifecycle — Spawn (on job_executing), idle animation, and dissolve (on job_complete) using Three.js animation and particle effects.

Relevant files

  • the-matrix/js/world.js
  • the-matrix/js/agents.js
  • the-matrix/js/effects.js
  • the-matrix/js/websocket.js
  • artifacts/api-server/src/routes/events.ts
## What & Why Making the type of work visually represented in 3D — a floating quill for writing, a spider for web research, brackets for coding, a lightbulb for brainstorming — transforms the Workshop from a waiting room into a place that reflects what's actually happening. ## Done looks like - Jobs are categorized (writing, coding, research, creative, analysis, other) - When a job enters `executing`, a category-specific 3D indicator object spawns near Gamma - The object rotates/bobs gently while the job runs; dissolves with a particle effect on completion - Purely client-side Three.js — no new server infrastructure beyond job category in WebSocket event - Graceful fallback: if no category available, a generic glowing orb is used ## Out of scope - Complex 3D meshes or external 3D assets (use procedural Three.js geometry) - Indicators for eval or payment phases (executing phase only) - Changing job execution logic ## Tasks 1. **Category broadcast** — Ensure job category is included in the `job_executing` WebSocket event (reuses categorization from performance dashboard task). 2. **Indicator geometry** — 5-6 simple procedural Three.js geometry + material combinations representing each job category; factory function. 3. **Indicator lifecycle** — Spawn (on `job_executing`), idle animation, and dissolve (on `job_complete`) using Three.js animation and particle effects. ## Relevant files - `the-matrix/js/world.js` - `the-matrix/js/agents.js` - `the-matrix/js/effects.js` - `the-matrix/js/websocket.js` - `artifacts/api-server/src/routes/events.ts`
replit added the workshopfrontend labels 2026-03-20 22:24:56 +00:00
gemini was assigned by Rockachopa 2026-03-22 23:37:42 +00:00
Collaborator

PR #102 created. Implemented 3D job type indicators with category-specific geometries, animations, and lifecycle management based on WebSocket events.

PR #102 created. Implemented 3D job type indicators with category-specific geometries, animations, and lifecycle management based on WebSocket events.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: replit/timmy-tower#16