head to head · open source

composio vs plandex

composio has 30,398 GitHub stars, 4,842 forks, 88 open issues and last shipped yesterday. plandex has 15,687 stars, 1,178 forks, 66 open issues and last shipped 1.0 years ago. composio leads on adoption by 94% (30,398 vs 15,687 stars). composio is written in TypeScript under MIT; plandex is written in Go under MIT. composio has attracted 16% as many forks as stars, plandex 8%. composio was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 5 topic tags (ai, ai-agents, developer-tools, gpt-4), so they are genuine substitutes rather than adjacent tools.

Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.

composio ★ 30K plandex ★ 16K category Developer Tools

← all 20902 open source comparisons

Side by side

composio plandex
GitHub stars ★ 30K ★ 16K
License MIT MIT
Written in TypeScript Go
Last push 2026-10-02 2025-10-03
Forks ⑂ 4.8K ⑂ 1.2K
Self-hosting Yes Yes
Data ownership Your server Your server

pick composio if

  • You weight community size — 30K stars and counting
  • You want the MIT license terms
  • Your stack matches TypeScript
  • You value the larger contributor base for long-term maintenance

full composio profile →

pick plandex if

  • You want the plandex feature set and don't need the biggest community
  • You prefer the MIT license terms
  • Your stack matches Go
  • You evaluated both and plandex fits your workflow better

full plandex profile →

About composio

Composio is an MIT licensed agent toolkit platform, distributed as TypeScript and Python SDKs, that gives AI agents more than 1,000 pre authenticated toolkits, per user sessions, authentication, triggers, and a sandbox for turning intent into action across real applications.

read the full composio overview →

About plandex

Plandex is an open source, terminal based AI coding agent for developers who need to plan and execute large coding tasks spanning dozens of files in real world projects.

read the full plandex overview →

More in Developer Tools

ECC ★ 271K react ★ 251K OpenCode ★ 211K vscode ★ 193K Langflow ★ 155K pi ★ 112K

Related comparisons

openclaw vs langflow ecc vs react ecc vs langflow react vs langflow ecc vs supabase react vs supabase n8n vs langflow ecc vs puppeteer openclaw vs openhands openclaw vs paperclip hermes-agent vs pi hermes-agent vs openhands hermes-agent vs paperclip opencode vs pi opencode vs openhands opencode vs paperclip react vs vscode react vs neovim react vs zed opencode vs neovim opencode vs zed vscode vs neovim vscode vs zed react vs kilocode

More Frameworks & Platforms projects

Compare either of these against the rest of the Frameworks & Platforms field.

composio vs ECC composio vs react composio vs Langflow composio vs Supabase composio vs puppeteer composio vs archify composio vs PocketBase composio vs i-have-adhd composio vs codebase-memory-mcp composio vs herdr composio vs ToolJet composio vs AppSmith

Frequently asked questions

Is composio or plandex more popular?

composio has 30,398 GitHub stars and plandex has 15,687. composio has the larger community by that measure.

Are composio and plandex free?

Both are open source. composio is licensed under MIT and plandex under MIT. Neither carries a licence fee.

What is the difference between composio and plandex?

composio is written in TypeScript and plandex in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, composio or plandex?

Choose composio if you want the larger community (30,398 stars) or its MIT licence terms. Choose plandex if its feature set, stack or MIT licence fits better. Both are self-hostable.