Key facts

Privacy
Runs in your browser; no inputs leave the page.
Cost
Free and offline after load.
Best use
Early architecture decisions before framework selection.
Boundary
Decision aid, not procurement or security approval.

Choose the right tool

Use them in order

Start with the readiness checker. If the verdict says prompt or workflow, use that answer as the design constraint and avoid agent theater. If the verdict says agent, generate a written spec before picking a framework. Only after the spec names tools, state, permissions, guardrails, and evals should you run the framework chooser.

The tools are intentionally conservative. They bias toward the least autonomous design that can do the job, because every extra tool and every extra autonomous step expands the test surface.

Sources used

  1. Agents SDK OpenAI Developer Docs. Accessed 2026-07-06.

    Defines agents as applications that plan, call tools, collaborate, and keep state.

  2. Building Effective Agents Anthropic Engineering. Accessed 2026-07-06.

    A practical distinction between augmented LLMs, workflows, and autonomous agents.

  3. LangGraph Overview LangChain Docs. Accessed 2026-07-06.

    Positions LangGraph as an orchestration runtime for durable execution, streaming, HITL, and persistence.

  4. CrewAI Documentation CrewAI. Accessed 2026-07-06.

    Introduces CrewAI agents, crews, flows, guardrails, memory, knowledge, and observability.

  5. OpenAI Agents SDK OpenAI. Accessed 2026-07-06.

    Documents the Python Agents SDK primitives: agents, handoffs, guardrails, tracing, sessions, tools, and sandbox agents.

  6. Agent SDK Overview Claude Code Docs. Accessed 2026-07-06.

    Documents Claude Agent SDK built-in tools, hooks, subagents, MCP, permissions, sessions, and production use cases.