Grok Bot: first-class Projects (roster, shared context, artifacts, status)

[monomyth (Eugene Ray)]

Feature request for product/service

– Other –

Describe the request

Summary

Grok Bot needs first-class Project support in the product UI and agent model — a way to group agents, shared context, assets, and status around a piece of work (e.g. a music video, a product launch), not just a flat list of unrelated chats.

Today you can spin up many specialist agents (producer + band, DP + crew) and they message each other, but the user has no project surface: no project home, no roster, no shared artifact shelf, no status rollup. Agents also lack a clear “this work belongs to Project X” boundary in the sidebar.

Motivation (real usage)

Running a multi-agent production (example: Orbital Drift music + music video) currently means:

• 1 Chief of Staff coordinating
• 1 music Producer + Composer / Drums / Bass / Synths / Critic
• 1 DP + Video Editor / Colorist / VFX Motion / Gaffer / Picture Critic
• Shared Mac paths, masters, markers, Imagine clips, Resolve project, Deliver mp4s
• Cross-agent handoffs (silent master → remux → Deliver)

That works only because humans/agents invent process in chat. The app treats every agent as a peer in one flat sidebar. Scaling past a handful of specialists gets noisy and easy to lose the thread of “what is the project state?”

[monomyth (Eugene Ray)]

Full ask (rest of the request):

1. Project as a first-class object — create / rename / archive a Project (e.g. Orbital Drift) with name, brief, cover, timestamps; a Projects list/tab, and opening one is the home for that work.

2. Project roster — attach agents with roles (Producer, DP, Editor, Critic…), show roster/org chart on the project page, have “hire a crew” scaffold agents into the project instead of orphan sidebar rows, and optionally group/hide specialists so the main sidebar stays leads only.

3. Shared project context — brief, decisions and constraints visible to all members; pinned artifact links (Live set, master WAV, markers, clips folder, Resolve project, current Deliver); clear separation of project vs per-agent vs global memory, with UI to browse/edit.

4. Status rollup — one view: what’s in flight, what’s blocked, latest master/Deliver, who owns the next gate. Fewer intermediate FYI pings.

5. Group room tied to the project — a default project chat (or channels) for crew traffic, separate from 1:1 with the lead agent.

6. Routines/automations scoped to a project — “new master lands in project exports → notify DP”; per-project bullets in the morning digest.

Current gaps: the flat agent list doesn’t scale to producer/DP org charts; there’s no single place for “current cut / master / open gates”; cross-agent coordination dumps into lead chats and creates noise; any hidden project concepts aren’t discoverable in the UI.

Nice-to-haves: project templates (“Music video crew”, “Band + producer”); artifact browser for box + connected Mac paths; permissions so only project members can shell into project folders; export project pack (brief + roster + artifact index).

Environment: Grok Bot early beta (desktop), multi-agent + connected Mac, heavy agent-to-agent messaging.

Ask: prioritize Projects as a product primitive — roster, shared context, artifacts, status — so a crew has a home that isn’t just a pile of chats.

[Colin]

Thanks for the feedback @Eugen_Eugen! Sharing it with the team.

And while this doesn’t solve cross-agent communication or artifacts, it might be useful for you to know that you can right-click on an agent and “Move to → New Section” to help better organize your list of agents. It’s a bit hidden!