Features
Providers
A provider is a coding agent CLI installed on your machine that Modula’s agents run on. Modula doesn’t ship a model or proxy any API calls: agents shell out to your CLI binaries, with your credentials, on your hardware.
Three provider types are supported:
| Type | CLI | Default config dir |
|---|---|---|
| Claude Code | claude | ~/.claude |
| Codex | codex | ~/.codex |
| OpenCode | opencode | ~/.config/opencode |
Before you add one
The CLI itself has to be installed and logged in first. Install it, run it once, and authenticate with its own login flow. Modula picks up the resulting config and credentials from the provider’s config directory.
Add a provider
From the Providers page, click + New Provider and fill in:
- Name: a label like
claude-personal. Several agents can share one provider, and you can add multiple providers of the same type (for example, two Claude providers with different config dirs for different accounts). - Type: Claude Code, Codex, or OpenCode. Picking a type pre-fills the default config dir.
- Config dir: where the CLI keeps its config and auth. The provider card warns you if the directory doesn’t exist.
Once saved, the provider becomes selectable on every agent and in chat. A provider can’t be deleted while agents still reference it.
Models
Models are chosen where the work happens, not on the provider: each agent can pin a model from its provider’s catalog, and each chat picks one per conversation. Leave the model unset to use the CLI’s own default.
MCP servers
Providers can carry managed MCP servers, which give agents extra tools beyond your code. The provider form includes presets for Jira, Linear, and GitHub, plus custom entries with a key, URL, and optional auth token. Modula writes these into the provider’s own config file, alongside (never overwriting) any MCP servers you’ve configured in the CLI yourself.
This is how tracker sync works: add the matching MCP server to the provider a scan agent runs on (Jira for jira-scan, Linear for linear-scan, GitHub for github-scan), and the agent can mirror your issues into the task list.
Local and self-hosted models
To keep everything on your machine, use an OpenCode provider pointed at a local or self-hosted model. Your code and prompts never leave your hardware, and the rest of Modula works the same.