Extensions are listed by contract (connector, guard, secret engine, MCP server), which tells an operator how an extension is wired but not what it is for.
Decided (maintainer, 2026-11-21): three groups, derived from the contract in one table in core, with no package manifest change.
Platform extensions: run or govern the platform. Guards and secret engines today; identity providers and runners later.
Integration extensions: connect outside systems. Connectors: events in, deliveries and actions out.
Agent extensions: change what an agent knows or can call. MCP servers today; agent profiles and tools when they become extension contracts.
Workflows and playbooks are package content, not extensions, and get no group.
Done when: the group is a function of the contract in one place in core, the API returns it with each accepted extension and marketplace entry, and the dashboard's extension pages show and group by it using the names above. Adding a contract without a group fails to compile or fails the gate.
Extensions are listed by contract (connector, guard, secret engine, MCP server), which tells an operator how an extension is wired but not what it is for.
Decided (maintainer, 2026-11-21): three groups, derived from the contract in one table in core, with no package manifest change.
- **Platform extensions**: run or govern the platform. Guards and secret engines today; identity providers and runners later.
- **Integration extensions**: connect outside systems. Connectors: events in, deliveries and actions out.
- **Agent extensions**: change what an agent knows or can call. MCP servers today; agent profiles and tools when they become extension contracts.
Workflows and playbooks are package content, not extensions, and get no group.
Done when: the group is a function of the contract in one place in core, the API returns it with each accepted extension and marketplace entry, and the dashboard's extension pages show and group by it using the names above. Adding a contract without a group fails to compile or fails the gate.
store.Contracts() in modules/connectors/internal/store maps each contract to its group: connector to integration, guard and secret engine to platform, MCP server to agent. Store.Upsert, the only way a package is stored, refuses a contract that isn't in the table, so a stored extension always has a group.
The API returns group on each accepted extension. GET /api/extension-kinds lists each kind with its label and group.
The dashboard's extensions page builds its tabs from that endpoint, under Platform extensions, Integration extensions and Agent extensions.
Not done: marketplace entries. The marketplace is still the legacy catalogue in internal/webui, keyed by old surfaces rather than contracts. It gets groups when it moves into the one binary. task check passed on the merged tree.
Done in 64ef2c9af, 23f23a6ca and d6f3a1a01.
- `store.Contracts()` in `modules/connectors/internal/store` maps each contract to its group: connector to integration, guard and secret engine to platform, MCP server to agent. `Store.Upsert`, the only way a package is stored, refuses a contract that isn't in the table, so a stored extension always has a group.
- The API returns `group` on each accepted extension. `GET /api/extension-kinds` lists each kind with its label and group.
- The dashboard's extensions page builds its tabs from that endpoint, under Platform extensions, Integration extensions and Agent extensions.
Not done: marketplace entries. The marketplace is still the legacy catalogue in `internal/webui`, keyed by old surfaces rather than contracts. It gets groups when it moves into the one binary. `task check` passed on the merged tree.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Extensions are listed by contract (connector, guard, secret engine, MCP server), which tells an operator how an extension is wired but not what it is for.
Decided (maintainer, 2026-11-21): three groups, derived from the contract in one table in core, with no package manifest change.
Workflows and playbooks are package content, not extensions, and get no group.
Done when: the group is a function of the contract in one place in core, the API returns it with each accepted extension and marketplace entry, and the dashboard's extension pages show and group by it using the names above. Adding a contract without a group fails to compile or fails the gate.
Done in
64ef2c9af,23f23a6caandd6f3a1a01.store.Contracts()inmodules/connectors/internal/storemaps each contract to its group: connector to integration, guard and secret engine to platform, MCP server to agent.Store.Upsert, the only way a package is stored, refuses a contract that isn't in the table, so a stored extension always has a group.groupon each accepted extension.GET /api/extension-kindslists each kind with its label and group.Not done: marketplace entries. The marketplace is still the legacy catalogue in
internal/webui, keyed by old surfaces rather than contracts. It gets groups when it moves into the one binary.task checkpassed on the merged tree.