Start your first Cockpit session

Before you begin#

• Use the MSOCK desktop application; Cockpit does not run on the web.
• Confirm SOCI Cockpit is enabled for your workspace.
• Confirm Claude Code is installed and signed in — the first-run Prerequisites step reports both.
• Open the correct workspace and understand which files the agent may inspect or change.

Run a first session#

1. 01

   Open SOCI Cockpit

   Select the SOCI Cockpit tile from MSOCK Studio, or use the module switcher in any module's header.

2. 02

   Check what grounds the session

   Look at the SOCK selector. It names the published harness this workspace's sessions answer from. If you want a different one, change it before starting the session.

3. 03

   Create a session

   Choose a model. Sonnet at High effort is the default and is a good first choice.

4. 04

   Send a bounded prompt

   Ask the agent to explain before changing anything, and name the specific subsystem or decision you care about.

5. 05

   Compare the two views

   Use the transcript for readable conversation and the terminal pane to inspect the real process output. They are the same session.

6. 06

   Try a lifecycle command

   Type /ws- to see the commands your workspace installed, or open the commands cheatsheet. /ws-ask is the universal entry point.

7. 07

   Leave and return

   Reopen the session and verify that the conversation is restored and the available terminal scrollback replays.

Explain the structure of this project and identify the files I should inspect before changing payment retry logic. Do not modify anything yet. Cite filenames and call out uncertainty.

Checkpoint#

• The grounding selection is the harness you intended.
• The model and effort match the task's complexity.
• The prompt has a clear scope and change boundary.
• Transcript and terminal reflect the same session.
• Reopening the session restores conversation context.

Next#