Command Studio
Your creator workspace: reusable command definitions, cross-server installs, drafts and the path to marketplace publication.
Command Studio at /dashboard/studio is the creator workspace. Where the builder edits one server's installed scripts, Studio manages your command definitions — source you own once and can install on any server you administer, then publish to the community marketplace.
What a definition is#
A definition is the canonical copy of a command you authored. It keeps:
- the KAL v2 source and its compiled program,
- a version number and changelog per version,
- the CONFIG schema (which becomes a settings form on every server),
- documentation you write for the marketplace listing,
- and its publication status.
The workspace#
| Action | What it does |
|---|---|
| Save draft | Keeps changes without activating anything; drafts may contain compile errors |
| Save & publish (private) | Compiles and marks the definition ready for installation |
| Install to server | Adds the current version to a server you administer |
| Submit to marketplace | Sends the definition for review (see Publishing commands) |
| Withdraw | Pulls a pending or published submission (existing installs keep working) |
| Delete | Removes the definition — blocked while servers still have it installed |
Definitions and installed scripts stay linked: a server installs a version, and the script page on that server can pull newer versions when you publish them.
Source protection#
Source you do not own is never shown. Opening someone else's definition (or a marketplace command you did not author) shows the structure — name, config schema, documentation — with the source replaced by a "proprietary and private" notice. Only the author and site admins can read source. Your own definitions are always fully visible to you.
Installing to a server#
From a definition, choose Install to server. The server receives the current version as an installed script with the CONFIG form prefilled from your defaults. Installing again does not duplicate — you are told it is already installed.
From Studio to Marketplace#
A definition that installs cleanly is one click from a marketplace submission. The review pipeline, versioning rules and what installers receive are covered in Publishing commands.