DistilCodeAll techniques

Technique 14 / 14

Task-specific tool adaptation

Keep exploration read-only, reserve graph queries for repository memory, and select compatible editing tools.

Interactive model

See the change.

Task: “Find the payment flow, then update the provider.” Compare a one-size-fits-all setup with role permissions and model-matched editing.

Role and model adaptationfocused permissions

Match capabilities to the work

Explore agent → locate payment provider files
  Glob / Grep / Read; no editing; graph calls denied

Codebase-memory → trace payment flow and callers
  Source search + codegraph_explore; no editing

Coding agent → update the payment provider
  Compatible GPT model: apply_patch
  Other models: edit / write

Graph access belongs to the repository-memory specialist.
The coding agent gets one compatible editing interface.

Conceptual demonstration. Counts illustrate the flow, not measured production savings.

How it works

Less context. Same thread of work.

Finding a call path and editing a file need different capabilities. The explore agent can search and read source without editing it. The codebase-memory specialist can also invoke codegraph_explore to trace relationships. Graph calls are denied for other agents, while smartbash focuses on shell and search work.

The active model also changes the editing interface: compatible GPT models receive apply_patch, while other models receive edit and write. Optional tools are selected by client, provider support, and feature flags. This avoids offering redundant editing interfaces and gives specialists a clear job-specific permission set.

Tool selection and authorization are separate. Model and runtime rules filter tool definitions; role permissions control which actions an agent may execute. A denied tool’s schema is not necessarily removed from every model prompt.

In practice

The operating loop

  1. 01

    Match the model

    The registry selects apply_patch or edit/write based on the active model family.

  2. 02

    Match the runtime

    Search, LSP, planning, phases, and code mode appear only when their provider, client, or flag conditions are met.

  3. 03

    Match the role

    Explore searches and reads; codebase-memory can query the graph; editing remains outside both read-only specialists.