Project Chat is a project-scoped message thread stored in the control plane. Use it for lightweight project discussion, handoff notes, Telegram text imports, and Telegram voice/audio recording cards that should stay with the project. Project Chat is not an execution surface. It does not talk to Codex, open a terminal, inspect files, select a host, or create branches. Use Main Chat or a workspace thread when you need host-side execution.

​
Project Chat, Main Chat, And Workspaces

​
Access Rules

Project Chat follows project access: Task-only readers stay on the constrained task board for the issues shared with them. They do not get Project Chat, Main Chat, workspaces, or execution access. Project Chat Telegram notifications follow the same access rule. Project members and project read-only users can opt into All messages notifications for a project. Task-only readers and the message author are never recipients.

​
Open Project Chat

1

Open a project

Sign in to the control plane and expand a project from the project navigation sidebar.
2

Select Project Chat

Click Project Chat under the project. The page loads the project chat thread from the control plane.
3

Send a message

If you are a project member, write a message and click Send. Read-only project users can read the thread but cannot send.

​
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.
Use Main Chat for:
  • 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.
Use a workspace thread for:
  • issue-focused implementation;
  • branch/fork workflows;
  • PR, push, merge, and rebase flows;
  • isolated worktree changes.