Make the project modular — support plugins for coding agents, locales, and other components

[dxcore35]

Context

I don't want to fork this project. I want to contribute to it directly.

Suggested feature

Make the architecture modular, so major parts of the app can become plugins instead of being built into the core. A contributor could then work in their own branch, build a plugin for one of these standardized "slots," and publish it — without needing to touch or fork the core project.

Some concrete plugin ideas, based on what the app already does:

• Agent engine plugins. Today the app supports claude, codex, and grok CLIs. A plugin system would let anyone add support for a new agent engine (Gemini CLI, a local Ollama model, a custom CLI wrapper) without a PR to the core engine code.
• Connected-app plugins. The app already has a marketplace over Composio for Gmail, Slack, GitHub, Notion, Linear, and more. A plugin format would let contributors add a new connected app themselves, instead of waiting on a Composio integration or a core PR.
• Computer/sandbox plugins. Bots currently get a cloud Linux desktop, a Local VM, or host control on macOS/Ubuntu. A plugin slot here would let someone add a new sandbox backend (a different cloud provider, a container runtime, a different OS target) as a drop-in module.
• Locale/language plugins. Right now the app is English-only. A plugin format for language packs would let contributors add and maintain their own language, without the core team owning every translation.
• Bot personality/template plugins. Pre-built "starter bots" (a coding reviewer, a research assistant, a support bot) could ship as installable templates instead of being hardcoded, so the community can share and swap them.

Why it matters

This turns the project into an ecosystem instead of one fixed codebase. Benefits:

• Contributors can add a new agent, connected app, sandbox, or language without waiting on the core maintainer.
• The maintainer's workload drops, since the core team can stay focused on core development instead of reviewing every single feature addition.
• Users get more choice, since the ecosystem can grow in directions the core team never has time to build themselves.

[milind-soni]

That makes sense, I will plan it out and start rolling it out in the next couple of release