← AI GitHub

AI GitHub

Crush for terminal coding with configurable providers

Run a terminal coding assistant with project context and connected tools.

Coding AssistantsPublished 2 min read

Key Takeaways

  • Crush combines a terminal interface, model provider configuration and tools for working with a project.
  • Start with a provider and a disposable directory.
  • Choose one provider and investigate a small module before granting broader tool access.
  • Provider context limits and tool support shape the experience.

How it works

Crush combines a terminal interface, model provider configuration and tools for working with a project. Extensions such as MCP connections can add capabilities to the session.

What you need

Start with a provider and a disposable directory. Inspect the configured tools and integrations before adding local credentials or connected services.

What to try first

Choose one provider and investigate a small module before granting broader tool access. Compare a focused edit against the project's formatter and tests.

Add a benign MCP tool with a similar name to a built-in command. Inspect which one the session calls and what confirmation the configuration requires.

Where to look for failures

Provider context limits and tool support shape the experience. Review connected servers and permissions independently of the model, because those components can read or change workspace data.

Related Franklin pages

Compare how each agent exposes tools and where extensions execute. Start from an empty extension set and add one capability at a time so access stays understandable.

For a library of development workflows that can complement a coding agent, see Franklin’s Superpowers profile. Superpowers

Project documentation

Try it for your workflow

Explore the project’s documentation for setup and usage, or save this page to a collection for later.

Read the project documentation ↗