# Continue — tools that shaped CodeVetter

> Canonical page: https://codevetter.com/inspiration/continue

The developer should be able to choose models and context sources.

## What we admire

Continue’s context-provider model makes the source of an AI assistant’s context more explicit. The openness to different models and local setups is a useful reference for a product that should not depend on one provider.

## The principle that stayed

Provider choice is strongest when the evidence contract stays stable. Swapping a model should not change the meaning of a verification receipt or quietly change the rules for a verdict.

## Where CodeVetter stands

CodeVetter supports user-configured providers while Rust-owned schemas keep CLI, MCP, and viewer aligned. Continue was a design study, not an integration.

## Sources

- [Continue context providers](https://docs.continue.dev/customize/deep-dives/custom-providers) — the creator's own source
- [CodeVetter codebase-context research](https://github.com/Codevetter/codevetter/blob/main/docs/knowledge/codebase-context-tools-landscape.md) — the CodeVetter project record

This is independent appreciation, not endorsement, partnership, code reuse, or feature parity.

## Public product links

- [CodeVetter](https://codevetter.com/)
- [Download](https://codevetter.com/download)
- [Documentation](https://codevetter.com/docs/)
- [Source](https://github.com/Codevetter/codevetter)