21 lines
1.3 KiB
Markdown
21 lines
1.3 KiB
Markdown
|
---
|
||
|
|
name: dev-server
|
||
|
|
description: Instructions on how to run correctly development / preview servers or background processes in new panes in cmux.
|
||
|
|
---
|
||
|
|
|
||
|
|
## When to use
|
||
|
|
|
||
|
|
This skill is active when the user asks directly or the agent wants to run a local dev/preview server or any other long running command that ideally needs to run in the background.
|
||
|
|
The idea is to provide a dedicated cmux pane / split where to execute this task, and skip entirely the background execution in the coding agent.
|
||
|
|
|
||
|
|
## How to use
|
||
|
|
|
||
|
|
1. Identify what is the task to run. Examples are `npm run dev`, `uv run manage.py runserver`, `python -m http.server` and so on.
|
||
|
|
2. Create a new split in cmux. By default we want to split right: `cmux new-split right`.
|
||
|
|
3. After the split is created, it will return some information like so: `OK surface:23 workspace:5`.
|
||
|
|
4. We want to rename the split to give it a meaningful name, for example "Django dev server" or "npm dev server": `cmux rename-tab --surface surface:23 "npm dev server"`
|
||
|
|
5. Now we need to send the actual command to the split: `cmux send --surface surface:23 "npm run dev"`.
|
||
|
|
6. Lastly, we need to send the <enter> key to trigger the command execution: `cmux send-key --surface surface:23 enter`.
|
||
|
|
|
||
|
|
The external process now is up and running. It will be up to the user to terminate or close the split.
|