CoreStudio installs one host-specific Skill and one shared CLI from the signed app already on your Mac. Use the bundled command-line installer, or choose your Agent 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.
Install CoreStudio
If CoreStudio is not installed, download the latest signed macOS release from GitHub. Installation itself does not need an open window. Start CoreStudio with Agent Bridge enabled only when connecting to a project; the target project does not need an open desktop tab.
Install without controlling a window
With local command access, run the bundled setup.sh for your host; no Computer Use or running Bridge is required. With browser-only access, ask the user to run that command once. Application Settings → Agent integration is an alternative.
Install the selected host
Use Install, Update, or Repair. CoreStudio prepares the host Skill and the shared CLI in one managed action.
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.
The command installs only the selected host. To install several hosts, pass their IDs sequentially, for example workbuddy qwenwork doubaowork. Use the actual app path if installed elsewhere. If setup.sh is missing in an older build, update CoreStudio or ask the user to install through Settings; do not run install.sh directly or download a replacement. Installation does not authorize image generation. Start CoreStudio later with open -b com.corestudio.desktop when project access is needed; login, browser authorization and starting a new host task may still require the user.
Agent connection guide
WorkBuddy
Use agent-browser or playwright-cli exposed by the current local task. A preview panel alone is not browser control.
Use a local WorkBuddy task. Install with the bundled setup.sh; ask the user to sign in only if login blocks progress.
Start a new task after installation. Confirm it discovers the CoreStudio Skill and browser skill; use the absolute CLI path in the Skill if PATH lookup fails.
Have the Agent open the chosen project’s Agent Board and read the rendered page before claiming it. A preview or downloaded HTML is not a successful connection.
The tested task did not expose native image generation. Check the current task’s tools. If unavailable, explicitly authorize CoreStudio generation as needed; its selected provider charges for usage.
QwenWork China
The tested route controls external Chrome through the official QwenWork extension. A controllable embedded browser and Edge were not validated.
Use a local QwenWork China task and install with the bundled setup.sh. Ask the user to sign in only if needed.
Enable Connectors → Installed → Browser in QwenWork. If waiting for the extension, check the official QwenWork extension in the Chrome profile you actually use; load it from the directory provided by QwenWork if missing.
Open the target Agent Board, click Connect in the extension, and confirm the current tab is connected. Restricted pages such as chrome://extensions cannot be used for this check.
Start a new QwenWork task to load the Skill and browser tools. If tools are still absent, copy the connection instructions from the original Board into the local task; do not refresh that page after copying.
Native image tools were discoverable in the tested task but generation was not invoked; availability depends on the account and task. Save a readable local image before writeback. CoreStudio generation requires separate authorization and uses its current configuration.
DoubaoWork
Use Operate Browser in a DoubaoWork Local Computer task. Cloud tasks cannot directly access CoreStudio on this Mac.
Sign in and run a Local Computer task once so DoubaoWork creates its default local skill directory.
Run the bundled setup.sh for doubaowork. If the directory is uninitialized, ask the user to start a Local Computer task instead of inventing a path.
Start a new Local Computer task to load the Skill, then use its browser capability to open and claim the chosen project’s Agent Board.
Visible-reference export and image writeback passed on the actual host. Native image tools were discoverable but paid generation was not tested. A chat preview alone is insufficient: obtain a readable local original. CoreStudio generation still needs separate permission.
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 state without changing project data; after a Board claim, project commands use the task session binding.
corestudio read status --json
Bind one Agent task to one project
Keep CoreStudio running with Agent Bridge enabled. The Skill creates a task session and binds it to the Agent Board project you claim; desktop tabs do not choose the target.
Open the CoreStudio project I choose, bind this task to its Agent Board, read the canvas and selection, then tell me what I can continue working on.
The Skill creates and reuses a process-scoped Agent session for Codex. Claiming a Board binds this task to that project, independently of desktop tabs.
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.
Read Local Bridge and current-project status without changing project data.
corestudio read status --jsonAgent session
Read the current canvas selection and stable image references.
Get the stable local Agent Board URL for the current project or project chooser.
corestudio read board-url --jsonAgent session
Write an existing local generated image and its actual final prompt through CoreStudio validation and persistence; omit the prompt only when none is available.
Match the visible symptom, take the shortest supported recovery path, and verify once before trying another change.
The Skill is installed, but browser tools are missing or QwenWork is waiting for its extension.
Use a local task; start a new task after installing the Skill or changing connectors.
Follow the selected host’s setup. For QwenWork, check the client switch, the official extension in the actual Chrome profile, and the target tab’s Connected state separately.
Without browser tools, copy the complete connection instructions from the original Board into the local task; keep that page open without refreshing.
The task reads the real page nonce and claims it, or explicitly completes CLI claiming with the original copied reference.
The host cannot access local files, or DoubaoWork’s default Skill directory is uninitialized.
Use a local task on this Mac. In DoubaoWork, sign in and run a Local Computer task once to initialize its default Skill directory.
Install the selected host in CoreStudio and start a fresh task. If the host option is missing, install an app version that includes it.
The local task discovers the Skill and uses its recorded absolute CLI path to read version and local status.
The Agent can show an image, but no readable local original is available for writeback.
Check the current task’s image tools and account capabilities; a chat preview is not an original file.
Save or download the generated original to a path readable by the local task, retain the actual final prompt and references, then write it through the CLI.
Export visible reference regions per element with read image-paths --visible; re-export expired temporary files. Use CoreStudio generation only with user authorization if native tools are unavailable.
The write receipt reports persisted: true and a record or canvas reread finds the result; never blindly retry paid generation.
The current Agent conversation may not have rescanned Skills installed after it started.
Start a fresh local Agent conversation and retry the same natural-language task.
Confirm the new conversation recognizes the CoreStudio Skill before running project commands.
The graphical Agent host may not inherit the terminal PATH that includes ~/.local/bin.
Let the installed Skill use the absolute CLI path recorded by CoreStudio.
Run corestudio --version --json through the path recorded by the Skill.
CoreStudio is not running, or the local session has not become reachable yet.
Open the installed CoreStudio app, wait for it to finish starting, then run read status once.
corestudio read status --json returns a structured status response.
The Bridge is available, but this Agent task has not claimed and bound a project yet.
Ask the Agent to list CoreStudio projects, open the stable project chooser, and claim the selected Board.
Read project with the same Agent session reports the intended bound project before any write operation.
The managed Skill, CLI wrapper, or integration contract is missing or out of date.
Open Application Settings → Agent integration and use Update or Repair for this host.
corestudio --version --json reports the current integration contract.
Agent sessions end when CoreStudio restarts.
Keep CoreStudio open and let the Skill establish a new Agent session for the current conversation.
Retry the read or write through the Skill and confirm the new session is accepted.
The Agent Board page was idle for a while, or CoreStudio restarted, so its room connection expired.
Use Refresh page in the Board recovery view to establish a new room connection.
The same stable Board reopens its bound project and returns to the editable canvas.
CoreStudio image generation is either not authorized for this host or no current provider is configured.
Review this host in Agent integration settings and configure the image service separately if needed.
Read capabilities reports supported, authorized, and configured as true before generation.
