Project Chat, Main Chat, And Workspaces
| Area | Project Chat | Main Chat | Workspace thread |
|---|---|---|---|
| Purpose | Project discussion and notes | Project-level Codex work | Issue or task execution |
| Runs on a host | No | Yes | Yes |
Requires jaidu-agent | No | Yes | Yes |
| Codex execution | No | Yes | Yes |
| Terminal and files | No | Host project root | Workspace folder |
| Branch/fork | No | No | Yes |
| Telegram import target | Yes | No | No |
Access Rules
Project Chat follows project access:| Access level | Can see Project Chat | Can send messages |
|---|---|---|
| Project member | Yes | Yes |
| Project read-only | Yes | No |
| Task-only read-only | No | No |
All messages notifications
for a project. Task-only readers and the message author are never recipients.
Open Project Chat
Open a project
Sign in to the control plane and expand a project from the project
navigation sidebar.
Select Project Chat
Click Project Chat under the project. The page loads the project chat
thread from the control plane.
Telegram Imports
Telegram can import text, voice, and audio into Project Chat. Text imports appear as normal Project Chat messages from the linked Jaidu user. Voice and audio imports appear as Project Chat recording cards with an audio player and transcript state. The linked Telegram account must belong to a Jaidu user who is a project member. Read-only project users and task-only readers cannot import Telegram messages into a project. Telegram is only an inbound Project Chat source. It does not make Project Chat an execution surface and it does not send anything to host-bound Main Chat. See Telegram for linking and import steps.When To Use Each Chat
Use Project Chat for:- project notes that do not need Codex;
- short coordination messages;
- Telegram plain text and voice/audio recording imports;
- context that should be visible at project level.
- Codex prompts against an existing host project root;
- host terminal commands;
- file and Git inspection inside the bound project directory;
- project-level planning through
/plan.
- issue-focused implementation;
- branch/fork workflows;
- PR, push, merge, and rebase flows;
- isolated worktree changes.