Lindy alternatives

+ Code-as-action agents in about a thousand lines of core code that work with any Hub model.
− Running model-written Python needs sandboxing, which is left mostly to you.

+ Unified provider interface and React hooks make streaming chat UIs trivial.
− Major-version upgrades have required significant rewrites.

+ Visual scenario canvas handles complex branching and iteration better than Zapier.
− Operations-based billing and error handling confuse newcomers.

+ MCP-first design means any MCP server becomes a Goose capability with no glue code.
− Less tuned for coding than Claude Code, so results vary widely by model.

+ Explicit state graphs with checkpointing make long-running agents debuggable and resumable.
− Steep learning curve and more boilerplate than simpler agent SDKs.

+ Largest integration catalogue of any framework, so almost any provider is one import away.
− Frequent breaking API changes and heavy abstractions make simple things feel over-engineered.

+ Inherits Claude Code's file, shell, and subagent tooling, so agents are production-grade on day one.
− Tied to Claude models and the Claude Code runtime rather than a provider-agnostic design.

+ Best-in-class document loaders, indexes, and LlamaParse for messy PDFs.
− Agent features are secondary to retrieval and the package surface is sprawling.

+ Role, goal, and task abstractions make multi-agent setups readable in a few lines.
− Agents can loop or burn tokens unpredictably with little low-level control.

+ Python-native components can be edited inline, so flows are not limited to built-in nodes.
− Several critical security vulnerabilities in 2025 made exposed instances risky.