devglow

List every registered project and AI process with its running state, port, PID, command, path and id. Projects are the user's permanent entries, started with start_project; AI processes are temporary ones created by run_process or workspace_run. Call this first: it gives you the ids the other tools take, and shows whether the user already has a project for the checkout you are working in. Also lists the tags already in use.

Takes no parameters.

Whether one project or AI process is running right now, with its PID. Lighter than list_projects when you already have the id, for example to confirm that start_project or stop_project took effect (both can return before the change has landed). 'No status found' means DevGlow has no entry with that id. For past runs, use get_run_history.

Recent finished runs of a project or AI process, newest first, with a summary: how long the command usually takes (median of successful runs), how often it succeeds, and how long it takes to start listening on its port. Use it when the user asks how long a build or script usually takes, whether it has been failing, or what happened on recent runs. Only finished runs are recorded; use get_status for whether it is running now. Commands are shown as recorded, with secret values masked as ***.

Get the full metadata for a single project or AI process (path, command, port, tags, description, status). Use this when you need details beyond what list_projects shows — for example, to duplicate a project with the same path, to reuse its command in a git worktree (then call run_process with the worktree path), or to read its description before editing.

Recent output of a project or AI process, oldest first, one line per entry as [timestamp] [level] message. Works whether it is running or stopped, but DevGlow keeps logs in memory only, so they are gone after the app restarts. Use it when a process exited, failed to start, or behaves unexpectedly. DevGlow writes the logs out on request, so the call can take a few seconds; if they do not arrive, DevGlow is probably not running.

Check if a TCP port is in use on localhost. When occupied, also reports who holds it — and if it's a devglow-managed project (so the user can recognize their own process). Call this BEFORE run_process / create_project to avoid silent conflicts.

Start a user-registered project with its registered command, in its registered path. Neither can be changed. PREFER this over run_process: call list_projects first, and if a project is registered inside the checkout you are working in, start it here instead of running the command yourself. Do NOT use this from a git worktree for a project registered in the main checkout: it would start the main checkout, not your worktree. Use get_project, then run_process with the worktree path.

Stop a running project or AI process by id (from list_projects). This is the stop tool to use for both kinds. The entry stays registered: a project can be started again with start_project. To remove an AI process instead of only stopping it, use delete_process. Returns once the stop is requested; call get_status to confirm.

Create and start ONE new temporary process. Shows in DevGlow's AI Processes section. User can later [keep] or [dismiss] it. A name already used by another AI process stops and replaces that process. Before calling this, run list_projects: if the user already registered a project inside this checkout, call start_project instead so you run THEIR command, not a new one. Only use run_process when no matching project exists. In a git worktree of a registered project, this IS the right call: a project registered for the main checkout would run there, not in your worktree. Detect a worktree with `git rev-parse --path-format=absolute --git-dir --git-common-dir` (the two differ only in a linked worktree), reuse the project's command, port and interactive flag from get_project, set path to the matching directory in the worktree, and name it '<project name> (<branch>)'. If you are starting more than one process, call workspace_run once instead of calling this repeatedly — otherwise each process waits in the sidebar and the user sees nothing happen.

Update a kept (permanent) DevGlow project's metadata. Pass only the fields you want to change. Does NOT apply to temporary AI processes — for those, set fields at run_process time or have the user keep the process first.

Register a permanent DevGlow project WITHOUT running it. This is how you 'add a project to DevGlow' — there is no config file to author (no devglow.json / DEVGLOW.md); calling this tool IS the registration. Use it for bulk registration when you want to record metadata only (no port binding, no browser tab, no dependency install). To start the project later, call start_project. Use run_process instead when you need to actually launch a server for verification or one-off work.

Delete a kept (permanent) DevGlow project. Stops the process if running. Does NOT apply to AI processes — use delete_process for those.

Stop and remove one or more AI processes (the temporary ones created by run_process / workspace_run) — the same as [dismiss] in the DevGlow UI. Use it to clean up processes you started once they are no longer needed. Does NOT apply to permanent projects; use delete_project for those. A pane that was showing a deleted process is left empty.

List DevGlow workspaces: id, name, which one the user is in, and the processes placed in each with their running state. Use it before delete_workspace, and to find workspaces left over from earlier work — one whose processes are all stopped or gone is a likely leftover. It cannot tell you who made a workspace; the user arranges them by hand too.

Takes no parameters.

Delete one or more DevGlow workspaces by id. Removes the arrangement only: the processes that were in it keep running and stay in the sidebar (use delete_process / stop_project for those). The workspace the user is currently in is refused — deleting it would replace their screen. Delete only workspaces you created or the user asked you to remove; list_workspaces first.

Stop an AI process by its exact display name. Prefer stop_project: it takes the id from list_projects, works for projects and AI processes alike, and the id is what every other tool uses. Use this only when you know an AI process by name alone. Does not apply to permanent projects. If no AI process has exactly that name, nothing is stopped, but the response still reads as sent.

Start two or more processes and arrange them on screen together in a new DevGlow workspace. PREFER this over repeated run_process calls whenever you are starting more than one process — the user does not have to ask to see them. Repeated run_process calls leave each process sitting in the sidebar until the user clicks it into a pane, so starting three that way makes the app look like nothing happened. Each process here starts exactly as run_process would. Always creates a new workspace: a name that already exists gets a numbered variant, and no existing workspace is ever modified, so a repeat call cannot disturb the user's arrangement. DevGlow chooses the split layout from its own window size; you cannot specify one. If DevGlow is closed it will be launched.