modloom.

Getting started

Core concepts

Projects, threads, runs, modes and credits in one page.

A handful of ideas explain almost everything in Modloom.

Project#

A project is one plugin: its source files, its history and its builds. Projects are private to your workspace. You can have up to 100.

Brief#

The brief is the description you started the project with. It is saved with the project and you can edit it on the project's brief page.

Thread and run#

The thread is the conversation with the agent about a project. Each message you send starts a run: one piece of agent work with its own steps, file changes and result.

  • Only one run is active per project at a time.
  • While a run is active, the editor is read-only so your edits and the agent's cannot collide.
  • You can cancel a run. Closing the browser does not cancel it.

Plan and Build#

A run has a mode.

  • Build edits files, runs Maven builds, fixes errors, and finishes with a commit.
  • Plan is read-only. It asks questions and proposes an approach without touching files.

Details are in Plan and Build modes.

Build and artifact#

A build compiles the project with Maven. A successful build produces the artifact, plugin.jar, which you download. You can also start a build yourself with Build plugin, with no model involved.

Modloom Credits#

AI work is metered in Modloom Credits. Planning and building both spend them, and heavier models spend more per request. Credits reset weekly. See Models and credits.

Workspace#

A workspace groups projects, a plan and usage. Limits such as credits and storage apply per workspace. See Workspaces.

Engine and version#

Your target is the server software (Paper, Purpur or Spigot) and the Minecraft version. It decides which server API the agent writes against and which Java version builds it. See Engines and versions.