Workspaces UI showing the four-panel layout with workspace sidebar, conversation, changes panel, and details sidebar
The Workspaces UI is the host-backed task execution experience for Jaidu. The control plane stores project state and routes requests, while the selected registered host runs Codex, owns files, and manages Git worktrees.

​
What is a Workspace?

A workspace is a host-side folder plus a Git branch for completing a coding task. Use it when you want to:
  1. Work on a specific task - Each workspace focuses on one goal (e.g., “Add user authentication”)
  2. Chat with Codex - Codex reads files, writes code, and runs commands on the selected host
  3. Review changes - See exactly what code was added, modified, or deleted
  4. Test your application - Built-in preview browser to see changes in action
  5. Create pull requests - Submit your changes for review when ready
Workspaces isolate issue-focused Codex work from your original repository folder. The control plane coordinates state, while jaidu-agent performs the filesystem, Git, terminal, preview, and Codex work on the host.

​
Key Concepts

ConceptDescriptionExample
WorkspaceA host-side execution folder and Git branch where you work with Codex”Add user authentication”
RepositoryA git repository included in a workspacefrontend, backend
ThreadA conversation thread with CodexCodex thread for implementing a feature
How they relate:
  • A workspace is your working environment for a specific task
  • A workspace can contain one or more repositories (each with independent git state)
  • Within a workspace, you can have multiple threads to restart context or separate independent workstreams
  • Branch/fork actions create a new workspace from the current workspace state
For example, you create a workspace for “Add authentication” that includes both frontend and backend repositories. Within that workspace, you might have one thread for implementing the backend API and another thread for the frontend UI.

​
Key Features

Multi-Repository Support

Work across multiple repositories within a single workspace. Reference code from one repo while implementing changes in another.

Multiple Threads

Run multiple Codex conversations in one workspace. Work around token limits by starting fresh threads while keeping the same files and Git state.

Workspace Branching

Fork the current workspace state into a new branch and worktree. Dirty workspaces get an automatic checkpoint commit first.

Browser Testing

Built-in browser preview without leaving the workspace. Test across desktop, mobile, and custom viewport sizes.

Changes Panel

Review code modifications with syntax-highlighted diffs. Add inline comments to provide feedback to Codex.

Integrated Terminal

Built-in terminal for running commands directly in your workspace. New to the Workspaces UI.

Workspace Notes

Notes for each workspace to document important information. New to the Workspaces UI.

Command Bar

Central navigation hub for quick actions. Access every workspace action with keyboard shortcuts.

​
Common Questions

When you create a workspace, the selected host:
  1. Creates a git worktree - a separate working directory linked to a new branch
  2. Your original repository stays untouched
  3. All changes happen in the worktree on a new branch
  4. Nothing is pushed to remote until you explicitly create a PR
Your main branch is safe. The workspace isolates all changes until you’re ready to merge.
Yes. Each workspace is completely independent:
  • Create as many workspaces as you need
  • Each has its own branch, changes, and threads
  • Switch between workspaces using the sidebar
  • Codex threads in different workspaces do not share branches or folders
You have full control:
  • Review changes in the Changes panel before committing
  • Add comments on specific lines to request fixes
  • Edit messages to retry with different instructions
  • Start a new thread if the conversation goes off track
  • Delete the workspace if you want to start completely fresh
Codex only modifies files in your workspace. It cannot push code or merge without your explicit action.
Watch for these indicators:
  • Status in sidebar changes from “Running” to “Idle”
  • Chat shows completion message or asks for next steps
  • Changes panel shows all modifications made
If Codex needs your input (approval, clarification), you’ll see a “Needs Attention” indicator with a raised hand icon.
  • Project = A container that groups related repositories (configured once in Settings)
  • Workspace = A task execution environment for a specific coding task
Think of it this way: A Project is like a team folder that contains your repos. A Workspace is a task you’re working on using those repos.