# How do I use an AI coding assistant without a big footprint?

> How developers can keep the benefit of AI coding assistants while cutting wasted tokens: right-size the model, focus the context, break tasks down.

Source: https://greenai.guide/how-do-i/use-an-ai-coding-assistant-with-a-smaller-footprint/  
Updated: 2026-11-19

## In short

Use the assistant where it clearly pays back, give it focused context rather than whole repositories, pick a smaller or faster model for routine edits, and break hard tasks into simple steps you review. One study found AI-assisted coding had around 33 times the carbon footprint of the manual approach on the tasks tested, so habits matter.

## Steps

1. Decide whether the task needs the assistant or is quicker to type yourself.
2. Choose a smaller or faster model for routine completions and edits.
3. Point the assistant at the relevant files rather than the whole repository.
4. Break a hard task into small steps and review each before moving on.
5. Set step or spend limits on agent modes and stop runs that loop.
6. Track your team's assistant usage alongside cost.

**Use the assistant deliberately, not by reflex, and keep what it reads small.** Coding assistants are useful, but
their energy is invisible to the person using them.

## Why does it matter?

Cheung and colleagues compared manual and AI-assisted development on a set of programming tasks and found the
AI-assisted approach had around 33 times the carbon footprint of the manual one, with the gap widening as tasks got
harder. That does not mean never use assistants; it means use them where they save real time.

Agent modes cost more again. Anthropic reported that its agents typically used about four times the tokens of a
chat, and multi-agent systems about fifteen times.

## What makes the biggest difference?

- **Context.** Every file the assistant reads is processed again on each turn. Open or reference only the files that
  matter, and start a new session for a new task.
- **Model choice.** Many tools let you pick a model. A small, fast one is usually enough for completions, renames and
  boilerplate; keep the large one for design and debugging.
- **Agent limits.** Give agents a clear goal, a stop condition and a step limit. See
  [how to stop AI agents wasting tokens](/how-do-i/stop-ai-agents-wasting-tokens/).
- **Small steps with review.** A person checking each step avoids long runs heading the wrong way.

## Common mistakes

- Letting an agent "fix the tests" in an open-ended loop.
- Regenerating a whole file to change one line.
- Accepting code without checking its efficiency: see
  [how to get AI to write energy-efficient code](/how-do-i/get-ai-to-write-energy-efficient-code/).

For the bigger picture, read [agentic AI and token waste](/articles/agentic-ai-and-token-waste/).

## Sources

- [Comparative analysis of carbon footprint in manual vs. LLM-assisted code development](https://doi.org/10.1145/3711919.3728678), Cheung, Kaul, Jahangirova, Mousavi and Zie, ResponsibleSE 2025 (ACM) (2025)
- [How we built our multi-agent research system](https://www.anthropic.com/engineering/multi-agent-research-system), Anthropic (2025)
- [GreenCode Constitution: agent principles for optimizing code and LLM inference energy use](https://greencode.ai/publications/greencode-constitution-agent-principles-for-optimizing-code-and-llm-inference-en/), Kapenekakis, Kim, Ionescu, Thomsen and Albano, GreenAI workshop, ECML PKDD 2026 (2026)
