Crush

Does it fit your conditions?

You prefer a terminal interface and can configure the provider and development tools.

Setup

Configure tools

Interface

Terminal

Access

Provider API key

Workspace

Independent workspace

Follow the current project installation guide and verify provider credentials and model support.

Reviewed scope: Charm's Crush project.

Coding and office fit

Provider and language-server setup depends on your local environment.

Costs and context

Provider usage

Track the selected provider's actual request usage, including retries.

Reduce unnecessary work: Locate a relevant symbol or error before requesting a broad repository scan.

Measured tokens / task

Unknown — not measured

Measured cost / task

Unknown — not measured

Compare the same deliverable and acceptance criteria, including retries and your review time. Local execution does not establish local model processing.

Try one real task

1. Follow the current project installation guide and verify provider credentials and model support.
2. Start with a small task: Investigate and edit a project using terminal and language tooling.
3. Check the result against your original files and acceptance criteria before expanding the workflow.

Before relying on this workflow, check the current plan, device, region, language, file format, and required permissions.

Bring your work with you

Bring project rules and task progress, then recreate provider and language-server configuration.

A reviewed brief can carry context. Native history, internal memory, account permissions, and running tasks are not assumed to transfer.