CoreStudio Agent integrations

Use CoreStudio in your Agent

CoreStudio installs one host-specific Skill and one shared CLI from the signed app already on your Mac. Choose your Agent, then finish setup in Application Settings → Agent integration.

The website explains the process. It does not inspect your Mac or run an installer.
Skill
Installed separately for each Agent host
CLI
Installed once and shared by all supported hosts
Connection
Local CoreStudio and Local Bridge

Install Skill and CLI together

Do not download a Skill archive or run a network install script. CoreStudio uses the integration resources bundled inside its signed application.

  1. Install and open CoreStudio

    If CoreStudio is not installed, download the latest signed macOS release from GitHub. Keep the app open for connection checks.

    Download latest release

  2. Open Agent integration settings

    In CoreStudio, open Application Settings → Agent integration. The website cannot open or inspect this local page for you.

  3. Install Codex

    Use Install, Update, or Repair. CoreStudio prepares the host Skill and the shared CLI in one managed action.

    ~/.codex/skills/corestudio/

  4. Start a fresh Agent conversation

    A conversation that was already open may not rescan newly installed Skills. Start a new local conversation before first use.

Verify installation before project access

Installation integrity and project connectivity are different checks. Start with the version command, then check the running app.

1. Installation integrity

This command does not require an open project or a reachable Local Bridge.

corestudio --version --json

2. Local connection

Run this after CoreStudio is open. It reports Bridge and current-project state without changing the project.

corestudio read status --json

Start with one natural-language task

Open a fresh local Agent conversation so the host can discover the new Skill, then ask it to open your current CoreStudio project.

Open my current CoreStudio project, read the canvas and selection, then tell me what I can continue working on.

Codex can establish its compatible local identity automatically. You do not need to copy a session reference.

Common CLI tasks

These examples are task entry points, not the complete contract. Agents should keep JSON output enabled and use the linked contract for full parameters.

Check status

corestudio read status --json

Read selection

corestudio read selection --json

Open Agent Board

corestudio read board-url --json

Write an image

corestudio write image /absolute/path/result.png --source-type generated --origin agent-board --json

Write a diagram

corestudio write diagram --format mermaid --file /absolute/path/process.mmd --anchor auto --json
Open the full CLI contract

Recover without stacking fixes

Match the visible symptom, take the shortest supported recovery path, and verify once before trying another change.

View source document