Code

AI coding tools for developers who want local or private assistance near the codebase.

Use this page when code completion, repository chat, terminal pair programming, or model-flexible development workflows need to stay inside your environment.

Repository context

Continue and Aider are useful when an assistant needs to read, explain, or modify code with project context.

Private completion

Tabby fits teams that want self-hosted code completion without sending the developer workflow to an external service.

Why it works

  • Self-hosted completion

    Tabby and Refact are closest when the main need is code completion, IDE assistance, and a private team-controlled backend.

  • Repo-aware assistance

    Continue, Aider, Cline, OpenCode, Codex, Qwen Code, Gemini CLI, and Void work well when an assistant needs to inspect, explain, or modify a repository.

  • Autonomous coding agents

    OpenHands fits heavier autonomous coding work where the agent needs a workspace, shell access, browser tools, or longer task execution under your control.

Curated repositories

AI developer tools

10 projects
TabbyML

TabbyML/tabby

TabbyML

33.5k

Self-hosted AI coding assistant

1.7k|Rust
NOASSERTION
aicodegencoding-assistant
continuedev

continuedev/continue

continuedev

32.8k

⏩ Source-controlled AI checks, enforceable in CI. Powered by the open-source Continue CLI

4.4k|TypeScript
Apache-2.0
open-sourcedeveloper-toolsai
Aider-AI

Aider-AI/aider

Aider-AI

44k

aider is AI pair programming in your terminal

4.3k|Python
Apache-2.0
chatgptclicommand-line
cline

cline/cline

cline

61k

Autonomous coding agent right in your IDE, capable of creating/editing files, executing commands, using the browser, and more with your permission every step of the way.

6.3k|TypeScript
Apache-2.0
Developer Tools & Integrations
anomalyco

anomalyco/opencode

anomalyco

150.2k

The open source coding agent.

17.3k|TypeScript
MIT
Agentic AI & Multi-Agent Systems
smallcloudai

smallcloudai/refact

smallcloudai

3.5k

AI Agent that handles engineering tasks end-to-end: integrates with developers’ tools, plans, executes, and iterates until it achieves a successful result.

309|Rust
BSD-3-Clause
fine-tuningself-hosteddeveloper-tools
openai

openai/codex

openai

78.2k

Lightweight coding agent that runs in your terminal

11.2k|Rust
Apache-2.0
Developer Tools & Integrations
QwenLM

QwenLM/qwen-code

QwenLM

23.9k

An open-source AI agent that lives in your terminal.

2.3k|TypeScript
Apache-2.0
Developer Tools & Integrations
google-gemini

google-gemini/gemini-cli

google-gemini

102.5k

An open-source AI agent that brings the power of Gemini directly into your terminal.

13.3k|TypeScript
Apache-2.0
geminigemini-apiai
voideditor

voideditor/void

voideditor

28.7k

No description provided.

2.5k|TypeScript
Apache-2.0
cursoreditorchatgpt

Selection guide

How to choose a private AI coding tool

The main split is server-based team completion, IDE assistants, terminal pair programming, and autonomous coding agents. Each solves a different developer job.

  • Tabby for self-hosted completion

    Best fit when a team wants an on-prem Copilot-style server, IDE extensions, repository context, and admin control.

  • Aider for terminal pair programming

    Best fit when developers want a CLI assistant that can edit multiple files, understand a repo map, and work through git diffs.

  • Continue for private-model IDE workflows

    Useful for IDE chat, edit, and autocomplete with local or private model backends, but weaker as a self-hosted server product.

  • Agents for multi-step code work

    OpenHands, Cline, OpenCode, Codex, Qwen Code, Gemini CLI, and Void fit better when the assistant needs to inspect a repo, run commands, or make multi-file changes.

Privacy fit

Private does not always mean fully self-hosted

Some tools run as local CLI or IDE clients that connect to private model endpoints. Others run a central server. Both can improve privacy, but they are different deployment models.

  • Centralized teams

    Tabby and Refact are stronger matches when teams need central deployment, code-completion control, or a private assistant backend.

  • Individual developers

    Aider, Continue, Cline, OpenCode, Codex, Qwen Code, Gemini CLI, and Void can be strong fits when a developer controls the model endpoint and workflow locally.

Workflow fit

Autocomplete, chat, or code changes

Rankable comparison content should explain whether a project is built for inline completion, repository chat, AI checks, terminal pair programming, or autonomous multi-file changes.

  • Do not flatten the category

    Tabby, Continue, Aider, OpenHands, Cline, and OpenCode all help developers, but they should not be presented as interchangeable Copilot clones.

Suggested additions

Strong candidates not yet in the registry

Roo Code

RooCodeInc/Roo-Code

8/10

An open-source VS Code coding agent with local and OpenAI-compatible model support. Strong fit, but suggested until the canonical repo is present upstream.

View repository

mini-SWE-agent

SWE-agent/mini-swe-agent

7/10

A lightweight coding agent for repo and issue-fixing workflows. Useful for agentic coding experiments, but narrower than IDE assistants and terminal pair programmers.

View repository

Plandex

plandex-ai/plandex

7.5/10

A terminal-based coding agent designed for larger tasks and multi-file plans. Relevant, but activity and fit should be reviewed before promoting it to the main list.

View repository

Trae Agent

bytedance/trae-agent

7.2/10

A software-engineering agent for coding tasks. Strong enough to watch, but less established in self-hosted developer workflows than the main curated tools.

View repository

Kilo Code

Kilo-Org/kilocode

7/10

An open-source agentic engineering platform and IDE assistant. Relevant to coding-agent intent, but should stay suggested until registry/source backing is clear.

View repository

Open SWE

langchain-ai/open-swe

7/10

An asynchronous coding agent from the LangChain ecosystem. Useful for background code tasks, but newer and more specialized than the main list.

View repository

DeepCode

HKUDS/DeepCode

6.8/10

An agentic coding project for paper-to-code, text-to-web, and backend generation. Interesting but more specialized than general private coding assistants.

View repository

Onlook

onlook-dev/onlook

6.5/10

An open-source AI-first design and React editing tool. Adjacent to developer tools, but stronger for visual frontend/design workflows than general coding assistance.

View repository

Related pages

Keep browsing

FAQ

Questions answered

What counts as an AI developer tool?

A self-hostable tool that helps developers write, review, understand, or navigate code while keeping the workflow private.

Should coding assistants live on the chat page?

No. Coding assistants have a different job: code completion, repository context, terminal work, and development workflows rather than general assistant chat.

What is the best self-hosted AI coding assistant for teams?

Tabby is the strongest fit when teams need a central self-hosted coding assistant with IDE extensions, repository context, and admin control. Refact is another team-oriented option. Continue, Aider, Cline, OpenCode, Codex, Qwen Code, Gemini CLI, and Void are better when individual developers control their local workflow and model endpoint.

How are Aider and Continue different from Tabby?

Aider is a terminal pair-programming tool that edits code through git-aware workflows. Continue is an IDE assistant that can use private or local model backends. Tabby is closer to a self-hosted server product for team code completion.

When should I use an autonomous coding agent?

Use OpenHands, Cline, OpenCode, Codex, Qwen Code, Gemini CLI, or similar tools when the job needs multi-file edits, shell commands, repository inspection, or longer task execution. Use Tabby or Continue when the job is mostly completion, chat, and inline editing.