Launch from the web app
Open a project on one of your connected computers from the web app. The coding app runs on that computer, not in the browser.
Before you start
Section titled “Before you start”Connect the project folder on the destination computer and have at least one toolkit. Use the same code-config.com account that connected that computer; another workspace member cannot launch on it for you.
The destination needs Code Config running and a usable coding app to complete the request. On a server, run csc listen. You can submit a request while a computer is asleep, but it cannot complete until the local software picks it up within the request’s time limit.
Send the launch request
Section titled “Send the launch request”- In Overview → Get back to work, choose your project. Alternatively, open Projects and choose the row’s Launch action or Launch here in its details.
- Choose the Computer where the project folder is connected.
- Confirm the Toolkit. A different selection is a One-time override; Use default restores the project or workspace default.
- Choose Open with. An unavailable app shows the reason beside its option.
- Read the destination summary, then choose Launch here.
Remember for this project saves the coding-app choice only, not the computer or toolkit. Only project editors can change it. Unchecking it clears that saved app preference.
Check it worked
Section titled “Check it worked”The panel reports Opened when the app opens on the destination computer. Check the project and tools there. Opened — one step needs attention means a setup or approval action remains; follow it before relying on that tool.
Managed launches appear under Sessions on the computer. A server launch may run inside tmux; use the attachment command shown by the panel to reach it from a shell on that server.
If it does not open
Section titled “If it does not open”| Result | Next action |
|---|---|
| That computer refused this launch | Sign in with the account that connected that computer. |
| Not picked up | Open Code Config there, or run csc listen on the server, then retry. |
| Launch timed out | Check the destination computer and retry. |
| No launch report | Check Sessions on the destination before submitting another request. |
| Launch status unknown | Choose Check request to inspect the same request rather than sending another. |
| No connected computers | Connect the destination computer. |
| Project isn’t mapped on a connected computer | Connect that project folder on the destination. |
| No toolkit yet | Create a toolkit or use a shared one. |
Progress reference
Section titled “Progress reference”| State | Meaning |
|---|---|
| Preparing request | The browser is preparing the request. |
| Sending request | The request is being submitted. |
| Waiting for your computer | The request exists and is waiting to be picked up. |
| Opening your workspace | The computer is opening the coding app. |
| Opened | The app opened on that computer. |
| Opened — one step needs attention | The app opened with an action remaining. |
| Already running | That app is already running in a tmux session. |
Troubleshooting explains tool-specific launch messages.