Graph Chat and voice
Beta: Graph Chat and voice are available for evaluation and may change as the experience evolves.
Choose workspace or project context for conversations and use voice when hands-free progress helps.
Before you begin
Decide whether the request is workspace-wide or project-specific. For voice, use a quiet environment and treat spoken approvals like written approvals.
What you will see
Workspace Chat · Beta is the navigation label for the workspace-wide screen, which shows a full-width conversation and message field. The page heading includes the workspace name followed by Workspace Chat, and its workspace scope identifies the screen. For project work, open Projects > selected project > Graph Chat · Beta; the project conversation is attached to the selected project and its scope is shown before you send a request.
The message placeholder says Ask Graph Chat to inspect, plan, or act across this workspace. Use project Graph Chat when the request should be attributed to one project.
Example requests
For a workspace answer:
For a project action:
The first request is read-only and workspace-wide. The second belongs in project scope because any follow-up should stay attached to that project.
Procedure
- For a workspace-wide request, open Workspace Chat · Beta at
/workspaces/:workspaceId/chat. For a project request, open Projects, select the project, then select Graph Chat · Beta; confirm the heading and selected project before sending. Each new-chat entry starts with an empty message field; a conversation is created only after you send a message or a supported project image. - Enter one bounded request in Message and select Send.
- Read the visible response and any proposed action before asking for follow-up work.
- Start voice when hands-free interaction helps, allow microphone access only for this intended session, and keep the same conversation.
- After voice ends, review the visible conversation and task or approval links before acting.
Expected result
The new message and response appear in the full-width conversation, with the workspace or selected project heading confirming where the request belongs. Starting voice continues the same conversation; it does not create a separate project or bypass an approval.
Permission guidance
Conversation scope follows membership and project access. Do not use a workspace conversation to bypass a project role.
Graph Chat migration: upgrade required
Old Tauri clients require a manual upgrade. Install the current Labor0 desktop release before using the renamed Graph Chat experience. Browser and mobile clients must also be on the coordinated release that contains the new route and conversation contract.
The old /assistant route and former workspace /workspaces/:workspaceId/graph-chat route are removed without redirects or compatibility aliases. Old bookmarks, links, and client requests do not resolve to Workspace Chat. Existing conversations remain available through their current thread links after the coordinated migration.
Keep Labor0 up to date before using the renamed experience. If Graph Chat is unavailable after an upgrade, install the latest Labor0 desktop release, update the browser or mobile app, or follow the upgrade instructions from your workspace administrator or Labor0 Support. Do not continue using an old client with the renamed experience. After upgrading, open Workspace Chat · Beta or Projects > project > Graph Chat · Beta for the intended scope.
If voice stops
Symptom: the voice session ends or does not respond. Likely cause: microphone permission, network interruption, or a session state change. Safe recovery: reconnect once, and continue in the message field if the issue remains. Review the visible conversation before repeating a request so you do not create a duplicate action.