studio

A local browser workspace for developing and releasing WordPress plugins. WordPress is a website platform, and plugins add features to it.

In plain words
What is it for?
Use it to manage local projects, edit files, run Plugin Check, open WordPress Playground, inspect package size, prepare SVN releases, and publish plugins with safeguards.
Why use it?
It puts common plugin work in one place instead of making you switch between separate tools and terminal commands.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/automattic/pressship/studio
Clone the repo
git clone --depth 1 https://github.com/Automattic/pressship
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,058 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03058
Opus 5 $0.00000 $0.01529
Sonnet 5 $0.00000 $0.00612
Haiku 4.5 $0.00000 $0.00306

Measured 2d ago against content hash 079f8f21a681, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

studio scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

website/docs/commands/studio.md · 311 lines

How it starts

The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Studio

Pressship Studio is the local web workspace for day-to-day WordPress plugin work. It brings the plugin list, local project registry, file editor, Plugin Check, WordPress Playground, AI assistance, package-size checks, ignore management, SVN release preparation, and guarded publish flows into one browser UI.

pressship studio

By default Studio binds to 127.0.0.1, opens your browser, and keeps running until you stop the terminal process with Ctrl+C.

Start Studio

pressship studio
pressship studio --no-open
pressship studio --host 127.0.0.1
pressship studio --port 9478

Options:

  • --no-open starts the server without opening a browser.
  • --host <host> changes the bind host. The default is 127.0.0.1.
  • --port <port> chooses the Studio server port.

Studio uses the same Pressship config directory as the CLI. You can see the active WordPress.org account, config directory, and current working directory on the Settings screen.

Requirements

Studio can open without a saved WordPress.org session, but the WordPress.org plugin list, review state, clone actions, and release credentials depend on pressship login.

For the full experience, have these available:

  • a saved WordPress.org session from pressship login;
  • local plugin folders with a valid plugin header;
  • svn for approved-plugin checkout, tag, switch, and release workflows;
  • WordPress Playground dependencies managed by pressship demo;
  • optional AI assistants such as Claude Code, Codex CLI, GitHub Copilot CLI, Cursor, Gemini CLI, OpenCode, or WP Studio.

Dashboard

Pressship Studio dashboard overview

The Dashboard is the starting point. It shows local plugins, WordPress.org plugins, running Playgrounds, account state, and AI assistant state.

Use it when you want to:

  • open a plugin in Studio;
  • add a local plugin folder;
  • refresh local or WordPress.org plugin lists;
  • jump to release management;
  • see whether AI assistance is enabled and ready;
  • inspect live internal job output when Debug mode is enabled.

Read the full file on GitHub · 311 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 311 lines · 0 tokens per session scan A 079f8f21a681

Subscribe to this mod's changes

studio is a command published in the GitHub repository Automattic/pressship (51 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,058 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.