Field noteNov 16, 20265 min read1 source

OhMyGame adds expanded plugin capabilities in beta 5.5

In one minute

OhMyGame’s beta 5.5 expands plugins from add-ons into extensions that can act on games, add workspace surfaces and bring their own model providers or agents. For builders of AI-assisted creative tools, the release makes the plugin boundary a place to compose both behavior and interface, while also making permission choices consequential.

What changed: OhMyGame beta 5.7 adds an app-store-style plugin browser with categories, recommendations, plugin detail pages, update sorting, and a view of plugins users create with AI.

What happened

WhiteTowerAI’s OhMyGame release notes mark v0.0.0-beta.5.5 as a pre-release dated November 6, 2026. The release adds a plugin marketplace that reads from a published index and offers only updates that the market allows. It also substantially broadens the work a plugin can do inside OhMyGame: plugins can run, capture and play a game, extend its preview, respond to hooks such as a finished turn or an image about to be generated, publish projects, add themes, add Canvas nodes, presets and chains, and supply their own model providers and agents.

The release adds a toolchain for plugin authors: an ohmygame-plugin command-line interface, a create-ohmygame-plugin template, development mode and export. The plugin authoring workflow also changes. The Plugin Builder runs as a project with the full project chat and can make every kind of plugin; the Plugins page is divided according to what a user wants to do. Project-specific panels are supported in .ohmygame/panels/: an agent can write them, and they appear beside chat once a user allows what each requests.

The notes describe permission and lifecycle changes as well. A user can review what a plugin asks for in plain, grouped lines; the release says installs, updates, errors and safe mode are clearer and safer. Each plugin now has one switch: adding or enabling it allows what it asks for, without a second approval, and projects can still switch it off themselves. Plugins that use newer manifest fields continue to install, while a new version removes older ones that no project uses.

Other changes in the same release include storing everything OhMyGame keeps for a project in that project folder’s .ohmygame/ directory, with existing projects moved when opened; recording project type in the root ohmygame.json; and adding project panels. The release also reports performance and reliability work, including lighter streaming replies, incremental file-tree loading and continuing a Codex conversation after a stop or failed request. The release notes identify this as a beta, not a general-availability launch.

What the archive adds

New Runtime’s earlier OhMyGame coverage described an open-source Electron studio where an AI agent designs, builds and playtests games. Beta 5.5 is a new fact on that story: it adds a broader plugin system and authoring path to the existing studio, rather than announcing a separate product.

Trend signal

This release supports agent-ready software exposing capabilities: plugins gain explicit ways to act on a game, extend previews and add workspace elements. It also makes the boundary’s permission model concrete. A single switch grants the plugin’s requested access, while projects retain the ability to turn it off; capability composition therefore depends on making those requests legible and controllable.

Why now

The release arrives as OhMyGame is still in beta and is building out the environment around its core game-making workflow. The notes group plugin marketplace, author tooling, project panels and project-local storage into the same release, suggesting an effort to make extensions usable across authoring, installation and project use rather than merely exposing plugin APIs.

Why it matters

A plugin system for an AI workspace determines more than which integrations users can install. It defines what an agent can do in its environment and how a project can present the results. OhMyGame’s plugin capabilities could let a team package game-specific actions, hooks and interface elements together with an agent or model provider. That is useful when a general-purpose assistant needs access to domain operations without every project recreating them.

The trade-off is permission concentration. One switch grants what a plugin requests, rather than asking for a second confirmation after installation. The plain grouped description and project-level off switch are meaningful safeguards, but they shift the practical review moment to installation or activation. Builders designing similar systems should treat capability descriptions and revocation as core product features, not administrative details. The project-local .ohmygame/ directory also points toward an operationally useful property: keeping project state alongside the project can make it easier to move or understand as a unit, although teams would still need to test how that behaves in their own workflows.

What happens next

  • OhMyGame will continue expanding the plugin ecosystem beyond beta 5.5’s initial capability set (6 months, 65%). Watch for: release notes adding plugin discovery, authoring or permission features.

Limits and uncertainty

The GitHub release notes establish what beta 5.5 is intended to add, but they do not quantify plugin adoption, reliability or the effect of these capabilities on game-development time. The release is explicitly a pre-release, so the behavior and APIs may change before a stable version. The notes describe a single plugin switch and project-level disabling, but do not establish how permissions are enforced internally or how users can audit actions after a plugin runs. Those implementation details and any independent security assessment remain unconfirmed here.

Skill to build now

If you are building an extensible agent workspace, sketch a capability inventory before adding plugins: list the actions, hooks, interface surfaces and provider access a plugin can request. Then make the activation boundary show those requests in grouped, plain language and include a project-level way to disable the extension. OhMyGame’s release makes both the capability set and the permission trade-off visible enough to use as a design review checklist.

Reader takeaway

OhMyGame beta 5.5 makes plugins a route for combining game actions, workspace UI and agents in one extension. Its permission design is just as important as its new capabilities: users can disable plugins per project, but enabling one grants its requested access without a second approval.

Evidence / sources

  1. 1github.com/WhiteTowerAI/ohmygame/releases
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicCodexExplore the codex topic hub.
  2. 02topicClaudeExplore the claude topic hub.
  3. 03topicClaude CodeExplore the claude-code topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract