Assist with Labor0

Beta: Assist features are available for evaluation and may change as Labor0 improves Graph Chat, voice, and messenger workflows.

Use Workspace Chat · Beta for broad questions. Use Projects > selected project > Graph Chat · Beta when a request should inspect or create work for one project.

Before you begin

Know whether the request belongs to the whole workspace or one project. For a messenger bridge, identify the Slack or Discord channel and actor who will be linked. Microsoft Teams and Mattermost are not currently supported or available for setup.

Choose a Graph Chat path

Request	Use	Example opening
Compare information across the workspace	Workspace Chat and voice	`Which projects mention an API migration? Return project names and source links only.`
Inspect or create work for one project	Projects > `selected project` > Graph Chat · Beta	`In this project, identify the smallest documentation task for the failing setup step. Do not start it yet.`
Let a team channel invoke project-scoped Graph Chat	Messenger bridges · Beta	In Slack, mention `@l0`; in Discord, use `/l0` after an active bridge is bound under Channel project routing

Keep sensitive answers, passkey prompts, and approvals in the authenticated app.

Expected result

A direct request appears in the selected Workspace Chat · Beta or project Graph Chat · Beta conversation and preserves its scope for follow-up. A messenger request resolves to the project bound under Channel project routing. If the response has the wrong project context, stop before creating work and repeat the request from Projects > project > Graph Chat · Beta.

Permission guidance

Conversation access follows the selected workspace or project. A Slack or Discord bridge also needs an installed provider, a linked actor, and a channel bound to the intended project.

Continue in the app

Open Labor0 to select the workspace or project and inspect Workspace Chat · Beta or project Graph Chat · Beta progress.

If Graph Chat cannot act

Symptom: Chat answers but does not create or continue work. Likely cause: the conversation is in the wrong scope or the actor lacks permission. Safe recovery: switch to Projects > project > Graph Chat, confirm the visible role, and repeat the request with a bounded outcome.