In this guide
  1. When you need to change an existing project
  2. When you need to choose the operating setup
  3. When data handling or authority matters
  4. Before accepting a result

When you need to change an existing project

For a defect or refactor, prepare reproduction evidence and acceptance criteria. Investigate before editing when the cause is unknown. The comparison guides focus on piloting equivalent tasks and reviewing the route to an accepted patch, rather than declaring a universal performance winner.

When you need to choose the operating setup

Decide whether the main need is terminal-driven work or continuous editor assistance. Configurable model access also creates configuration and billing responsibilities. Use the product guides to inspect the working loop and the cost guides to separate fixed fees, variable usage and maintenance.

When data handling or authority matters

Data destinations and action authority are separate requirements. Even local inference needs verification of auxiliary features and integrations. The permissions guide separates investigation, editing, execution and release; the local-model guide covers hardware and network behavior as part of the complete configuration.

Before accepting a result

Verify explainability and handoff as well as visible functionality. Review test expectations, database compatibility and deployed behavior in sequence. Completing one contained task gives you stronger adoption evidence than generating a large volume of changes without knowing which ones remain maintainable.

Official sources

Pricing, availability and feature limits can change. Check the linked official pages before subscribing.

How we compareAdvertising disclosure