Select a project to get started.
See what needs attention, what is active, and what comes next.
Chat with Qwen, inspect your project, and review every proposed change before it runs.
Images go to the assigned lead model when you send.
Give Qwen extra tools and specialist help. Each plugin call and consultation appears in Activity and needs review.
Connect an installed local MCP server. Studio starts it only after you approve discovery or a tool call. Plugins run with your Mac permissions.
Uses the plugins and agents configured in your Codex CLI. Codex keeps its own permissions; actions needing interactive approval may be unavailable here. Manage installation and sign-in in Codex.
Search the official MCP Registry. Local npm and Python packages can be prepared for Studio. Remote connections and account setup are labeled separately.
Catalog descriptions come from publishers. Adding prepares a disabled entry for your review. Enabling and approving a call may download and run the package.
Credentials are saved in this Mac’s Keychain. They go only to this plugin when you approve a connection test or tool call.
Archive hides an item and keeps its history. Delete removes studio history and knowledge; project source files remain on disk.
Create a separate named account for every person. Administrators can manage settings and accounts; members can work with projects.
Choose the services and limits used for project work. These settings are saved on the JCE host.
Add folders already available to this host, including mounted Synology shares. JCE checks access and capacity, but never mounts, unmounts, or deletes the underlying storage.
Listener, public URL, reverse proxy, and operating-system mounts are machine-level settings. They are shown here for clarity and require a service administrator to change.
Tab status works automatically. Desktop notification status is loading.
A project connects one folder on this Mac with its own conversations, files, run settings, tests, and project knowledge. Choose one lead model to own its work from start to finish.
No project folder selected yet.
The lead inspects, implements, tests, repairs, and reports completion. You can explicitly reassign the project later.
The new model will continue from the current project files, saved checkpoints, tests, and conversation history.
Anyone with the access key can use this Mac’s projects and approve commands. HTTP is unencrypted: use only on your trusted LAN. Do not forward this port to the internet.
Use your JCE account to continue.
Qwen receives applicable rules on every turn. Your instructions and Studio permissions take precedence. Requirements below are a draft from your request; planning is not proof that they work.
These permissions apply only to this project. Turn on Unattended when sending a task. Tests and independent Codex completion review remain required.
Select up to 12 checks found in this project. You do not need to type commands. Nothing runs when you select a check.
Installs and publishing still need your approval. If no checks are found, ask Qwen to set up tests first, then refresh. Launch recipe changes require saving these permissions again.
Builds and preview commands run project code with your Mac account’s file and network permissions. This is an approval policy, not an operating-system sandbox. Only authorize code you trust.
Anything outside these permissions stops with saved progress and “Needs your help.” Limits stop the task. Stop and time limits also stop previews started by that task. Successful tasks leave their preview available. No automatic restart after quitting Studio.
Keep this conversation and its full history. Future messages can use the selected project’s files and reviewed tools.
Build and run automated tests on a Windows computer over SSH. Use an existing SSH host alias with key authentication and a verified host key. No passwords are stored in Studio.
Each reviewed build or test sends a bounded source snapshot to a fresh Windows folder. Logs return here; artifacts stay on Windows. SSH does not provide interactive GUI testing. Disconnecting may leave remote work running.
Use Windows PowerShell or cmd.exe as the SSH default shell. Commands run with the configured Windows user’s permissions. Use normal platform setup; Studio does not disable security protections.