What's inside a quadrant?

A quadrant is one project's workspace, and everything for that project sits in it. Filling most of it is the main terminal, where the coding agent (your selected supported provider) runs and you type to it. The top bar holds the project, start, preview, sleep, menu and project-settings controls. A bar along the bottom holds the permanent Agent / Chat switch, DevTools, and the Terminals drawer. Beside the quadrant is a side panel with tasks, done, and notes tabs plus an expand button for a larger view.

The parts

• Main terminal: the big panel where you talk to the agent. Press Enter to send, Shift+Enter for a new line, and answer its menus with the arrow keys and Enter, not the mouse. When the agent mentions a project file such as src/App.tsx:42, it becomes a link: click it to open that exact file and line in the project DevTools drawer. The corner microphone is optional and hidden by default; turn it on under Settings → Codus Whisper → Microphone buttons on Agents if you want to speak straight into terminals. Chat's microphone is unaffected. See provider, model and reasoning settings.
• Project terminals: the Terminals button at the bottom-right slides a drawer up from the same edge. It shows two comfortably wide terminals at a time and scrolls sideways when there are more: npm run dev (your dev server), npm run workers (a queue or scheduler), and freehand (a plain shell for one-off commands you type yourself) are included by default. The drawer starts and stays on those leftmost terminals until you scroll right yourself. Every terminal you add keeps the same width instead of squeezing the others smaller or pulling the drawer away from the left. Double-click any terminal title to rename it for this project; press Return to save or Escape to cancel. This changes only the friendly label, not the command or agent underneath. Use + in the right rail to add another terminal, a Claude Code agent, or a Codex agent using GPT-5.6 Sol. Added agents can be Builders or review-focused Reviewers. Both have full project access without permission pop-ups, and each has its own inbox so it can speak directly to the Lead Agent or another added agent. The rail scrolls when it fills up. Each terminal can be tucked into that rail or expanded into the quadrant's large main view; while a project terminal is large, the special Agent rail returns you to the Lead Agent, which has kept running in the background. Closing the drawer, minimising a pane, or switching the large view does not stop anything or clear its output. If your project does not start with npm, open the project-settings modal and change Start commands. See running more than one agent.
• web: the globe button opens a built-in preview browser in the slot next to the quadrant, so you can watch the app the agent is building. See the web button.
• Project DevTools: the DevTools button in the quadrant's bottom bar opens a large side drawer with Changes, Explorer, History, PRs, and Actions. It fills the usable height between Codus's top and bottom bars and stops at the nearest edge of the quadrant that opened it, so that quadrant remains visible. Left-hand quadrants open it from the right; right-hand quadrants mirror it from the left. Terminal file links use this same drawer and jump straight to the exact file and line. See DevTools.
• Web inspector: with the preview open, its </> button (or Cmd+Option+I) opens Chrome's page inspector next to the preview, together with the same project tools. Use this entrance when you need the website console, elements or network requests. See DevTools.
• Agent / Chat: the two-way switch at the bottom-left changes only what you see. Chat lays a plain-language conversation over the still-running Agent terminal, and a message at the top says so. A red dot on Chat means the agent has asked you something. See the chat panel.
• Sleep: the eye dims a quadrant you are not using, showing its name and the last thing it finished. The agent keeps running. See sleeping a quadrant.
• Assets: opens the project's asset library, separate from terminal output and source-control history.
• Menu: the three lines open a panel over the quadrant holding its less-used actions, including plan.
• Side panel: the tabs beside the terminal are tasks (work you queue for the agent), done (a log the agent adds to as it finishes things), and notes (things you want to keep). The expand icon at the right end of that row opens the same project information in a large modal, with the quadrant, folder and branch named at the top.

How do I know it worked?

The header names the intended project, and the terminal, sidebar, browser or Assets control opens that project's surface. A running agent and a running project server are separate things to check.