Osy#the first language built for agents
Agents firstAgentic appsWorkflowsDurable Execution — built inSecurityTestingThe editorThe UI modelOne program

Reference / Local

Listing your local platforms

osy instances [--running] [--all] [--stale] [--json]

Lists every local platform on this machine and says which are still running. The build-and-test loop starts one per project on demand, so this is how you find the ones you left up — and which project each belongs to.

stablelocalcli

Summary#

Shows every local platform this machine has, and which of them are running right now. Each project gets its own — the loop commands start one on demand (Running a local platform) — and Stopping the local platform stops exactly one, the project you are standing in. This is the other half: seeing what is up before deciding what to stop.

Signature#

osy instances [--running] [--all] [--stale] [--json]

Description#

Running platforms are listed first, each with its URL, the process behind it, and how long it has been up. A platform counts as running only when the process it recorded is verified to still be that process — a recorded process id on its own is not proof, because the system reuses ids, so anything unproven is reported as such rather than guessed at.

  • --running lists only the platforms with a verified live server.
  • --all also lists directories that have never run a server. Working in a throwaway project leaves one behind, so these accumulate; they are counted in the summary line by default and printed in full with this flag.
  • --stale lists only the platforms whose project directory no longer exists.
  • --json emits the list for tools and agents.

The summary line reports the total disk all of them occupy. Each carries a database of its own, so the figure grows faster than the count suggests — Reclaiming the disk your local platforms use deletes the ones you have finished with.

Listing never signals anything — it only reads. To stop one, go to its project and run osy stop, or name it directly with osy stop --devname <name>. Stopping a platform by killing processes by name is never the right move: another project's platform, or a test run, can be caught in the same sweep.

Examples#

osy instances --running     # just what is still up
osy instances --json        # the same list, for a tool to read

See also#

Reclaiming the disk your local platforms use — delete the ones you are no longer using.

Stopping the local platform — stop one of the platforms this lists.

Running a local platform — what a local platform is, and how the loop starts one per project.

Launching your app — compile and open your app, starting a platform if there isn't one.

Related

Reclaiming the disk your local platforms use

Each local platform carries its own database, so they add up fast. This deletes the ones you are no longer using —…

Stopping the local platform

Stops the local platform serving your project — the one the build-and-test loop starts on demand. Its database stops…

Running a local platform

Runs a full platform on your own machine — its own database, no account, no cloud, reachable only from your computer…

Compiling your app

Compiles your app's source into the app on the local platform — the inner-loop compile-and-apply. It applies additive…

Launching your app

Opens your app in a browser, running on the local platform. It compiles the current source first, so what opens…

Running tests locally

Runs your app's tests against a Platform on your own machine — no account, no network, no setup beyond a running local…