Development

Contribute to Turboism or develop with Java, GraalJS, and MCP.

Contribute to Turboism

Read Contributing to work on Turboism itself.

Start here: build your first plugin

New to Turboism plugins? Follow Build Your First Plugin, a six-step tutorial that takes you from the project template to an installed, tested plugin with a menu command, live Cubism data, and a saved setting. The Key Mechanisms pages explain lifecycle and cleanup, permissions and availability, threads and tasks, and how to diagnose a plugin that does not load.

Java plugins

Use Quick Start, Plugin Interfaces, Plugin Manifest and Packaging, and Designing Plugins. Java plugins are Java 17 JARs loaded in process and use the public SDK lifecycle and services.

GraalJS scripts

Read GraalJS Scripts for restricted scripting. A Java caller must explicitly run a script through ScriptService; discovery does not execute it automatically, and scripts do not receive the complete Java SDK.

MCP

Read MCP when a trusted external client needs authenticated loopback Streamable HTTP automation. MCP is not an in-process plugin API.

Coding-agent context

LLM Coding Context is a vendor-neutral project brief for coding agents. It is not another development approach.

ACP is provided by the first-party ACP Agent plugin. It launches a user-installed ACP-compatible agent and connects it to Turboism MCP through a local stdio bridge. It is separate from Java plugin APIs and no longer depends on the retired fx runtime.