Large development tasks rarely involve a single conversation.

With tmux, you can dedicate a Codux session to a specific objective and keep that context alive while you work.

Window 1 - Feature Development
Implementing a new gameplay system
Codux focused on design decisions, code generation, and implementation details

Window 2 - Code Review
Reviewing your current branch
Codux focused on bugs, edge cases, performance issues, and refactoring opportunities

Window 3 - Debugging
Investigating a failing test or runtime issue
Codux focused on logs, diagnostics, stack traces, and root-cause analysis

Window 4 - Architecture
Planning larger changes
Codux focused on project structure, APIs, and long-term design decisions

Each Codux session maintains its own conversation and context.

Instead of constantly changing topics within a single AI conversation, you can keep dedicated Codux sessions attached to specific workflows and switch between them instantly with tmux.

Use :CoduxWorkspaceCreate or <leader>zw inside tmux to create a guided Codex workspace. The create flow prompts for a name, lets you choose none, a workspace template, or custom, then previews the instruction before launch. New workspace windows launch in the current file or explorer target's project root, so the workspace follows the same worktree and branch as the code you are working on.

Inside tmux, Codux creates or reuses a backend-debug window in the current tmux session, restores Neo-tree to the same target when available, and starts new workspaces with your current Codex permission profile. Reopened saved workspaces keep their stored profile. Template workspaces use the requested workspace name for the tmux window. New template and custom-instruction workspaces open the Codux popup so you can confirm the startup prompt is running.

Workspace names are persisted per project in stdpath("data")/codux/workspaces.json. Creating a workspace with an existing name shows workspace already exists.

Use :CoduxWorkspaces or <leader>zW to open current codux workspaces. From that window, press <CR> to open a saved workspace, r to rename it, d to delete it, or h to run doctor. Statuses show active, inactive, or missing. The target column updates as each workspace moves between files or supported file explorer targets.

Outside tmux, Codux shows no tmux session running and does not create a workspace.

Workspace names are user-defined and sanitized for tmux window safety. Empty names and sanitized-name collisions are rejected with a clear error.

Create task-specific Codex workspaces with built-in templates:

:CoduxWorkspaceCreate fix-tests --template debug
:CoduxWorkspaceCreate add-feature --template implementation
:CoduxWorkspaceCreate review-pr --template review
:CoduxWorkspaceCreate token-review --custom

Templates provide task-specific starting instructions for Codex without starting autonomous loops. The template picker includes a separate search bar and supports <CR> to select, <C-e> to edit a saved template, <C-d> to delete the highlighted template, or <C-q> to cancel. The guided create preview lets you press <CR> to create, e to edit the instruction for just this workspace, or q to cancel. Custom instructions open in a Vim-like multi-line scratch editor with bottom command hints; use :w to save or :q to cancel. Saved custom instructions become reusable templates named after the workspace and appear in future template lists. A newly created template workspace opens Codux visibly for confirmation; regular workspaces keep the hidden startup behavior. Built-in templates include implementation, debug, review, planning, and docs. Codux stores the resolved startup instruction with the workspace so future template edits do not change what that workspace was created with.

require("codux").setup({
  workspaces = {
    templates = {
      release = "You are working in a release workspace. Focus on verification, notes, and final checks.",
    },
  },
})

Use :CoduxTemplateList and :CoduxTemplatePreview <template> to inspect available templates. Use :CoduxTemplateDelete <template> to remove a saved template or hide a built-in/configured template from future template lists. Long-form commands are also available: :CoduxWorkspaceTemplateList, :CoduxWorkspaceTemplatePreview, and :CoduxWorkspaceTemplateDelete. Workspace and template commands support tab completion.

Use :CoduxWorkspaceRestore to reconcile saved workspace state with tmux after restarts. Use :CoduxDoctor, or press h in the workspace dashboard, when troubleshooting external dependencies and saved workspace targets.