Found while executing #102. That card's dispatch cites os studio as live evidence that Studio survives as a named surface, so the command was measured rather than assumed — and it does not exist.
What the docs say
content/docs/reference/cli.mdx:74, on origin/main at 514527b:
os studio — dev server with the UI enabled
Same as os dev but with the UI explicitly enabled.
What ships
Measured on objectstackorigin/main at 2866d5f97e:
packages/cli/package.json configures oclif with "commands": { "strategy": "pattern", "target": "./dist/commands", "glob": "**/*.js" } and no alias map, so the shipped command set is exactly the files under packages/cli/src/commands/.- That directory holds:
build, cloud/, compile, create, data/, datasource/, db/, dev, diff, doctor, environments/, explain, generate, i18n/, info, init, lint, login, logout, meta/, migrate/, package/, plugin/, register, serve, start, validate, verify, whoami. There is nostudio command, and a case-insensitive grep for studio across packages/cli/src returns only comments, i18n baselines and tests — never a command definition. - Control probe for that zero: the same greps do return
dev.ts and serve.ts, so the pattern is not silently matching nothing.
The nearest live thing the CLI says about Studio is the opposite of a command — packages/cli/src/commands/serve.ts:2470-2472:
@objectstack/studio is intentionally NOT default-loaded — the console ships a dedicated Studio surface at /_console/studio/<pkg>/<pillar>, so Studio no longer needs to exist as a navigable app tile.
Not invented here — inherited
objectstack's own packages/cli/README.md:45 still lists | os studio [config] | Launch Studio UI with development server |, so this repo transcribed an upstream line that has gone stale. Whoever fixes this should decide whether an upstream companion issue is wanted; the two claims are not even the same claim ("dev server with the UI enabled" here vs "Launch Studio UI with development server" there), which is itself a sign nobody has run it lately.
Why it is worth recording
The command is documented in the CLI reference under its own heading, so a reader trying to open Studio types os studio and gets an oclif "command not found". The real route is os dev / os serve and then /_console/studio in the browser — which #102 now defines in the glossary.
This does not disturb #102's ruling. That ruling rests on studio.access (a live, enforced entry capability) and on the console's shipped /_console/studio surface, both measured; os studio was only ever a third, weaker leg of the same argument.
What settling it looks like
One of: delete the os studio section; or replace it with the accurate instruction (os dev, then open /_console/studio). Deleting is cheaper and loses nothing, since os dev is already documented directly above it. Needs a call on whether the upstream README is fixed in the same round.
Related: #102.
Found while executing #102. That card's dispatch cites
os studioas live evidence that Studio survives as a named surface, so the command was measured rather than assumed — and it does not exist.What the docs say
content/docs/reference/cli.mdx:74, onorigin/mainat514527b:What ships
Measured on
objectstackorigin/mainat2866d5f97e:packages/cli/package.jsonconfigures oclif with"commands": { "strategy": "pattern", "target": "./dist/commands", "glob": "**/*.js" }and no alias map, so the shipped command set is exactly the files underpackages/cli/src/commands/.build,cloud/,compile,create,data/,datasource/,db/,dev,diff,doctor,environments/,explain,generate,i18n/,info,init,lint,login,logout,meta/,migrate/,package/,plugin/,register,serve,start,validate,verify,whoami. There is nostudiocommand, and a case-insensitive grep forstudioacrosspackages/cli/srcreturns only comments, i18n baselines and tests — never a command definition.dev.tsandserve.ts, so the pattern is not silently matching nothing.The nearest live thing the CLI says about Studio is the opposite of a command —
packages/cli/src/commands/serve.ts:2470-2472:Not invented here — inherited
objectstack's ownpackages/cli/README.md:45still lists| os studio [config] | Launch Studio UI with development server |, so this repo transcribed an upstream line that has gone stale. Whoever fixes this should decide whether an upstream companion issue is wanted; the two claims are not even the same claim ("dev server with the UI enabled" here vs "Launch Studio UI with development server" there), which is itself a sign nobody has run it lately.Why it is worth recording
The command is documented in the CLI reference under its own heading, so a reader trying to open Studio types
os studioand gets an oclif "command not found". The real route isos dev/os serveand then/_console/studioin the browser — which #102 now defines in the glossary.This does not disturb #102's ruling. That ruling rests on
studio.access(a live, enforced entry capability) and on the console's shipped/_console/studiosurface, both measured;os studiowas only ever a third, weaker leg of the same argument.What settling it looks like
One of: delete the
os studiosection; or replace it with the accurate instruction (os dev, then open/_console/studio). Deleting is cheaper and loses nothing, sinceos devis already documented directly above it. Needs a call on whether the upstream README is fixed in the same round.Related: #102.