Codeme
A local coding assistant with repository context, streaming conversations, and explicit approval for workspace changes.
THE PROBLEM
What it sets out
to solve.
A coding assistant needs grounded project context and visible tool activity without handing consequential workspace actions directly to a model.
THE APPROACH
How it comes
together.
An Angular client and VS Code sidebar talk to a FastAPI backend. The backend persists conversations in SQLite, gathers allowlisted workspace context, and runs a local Ollama tool loop. The VS Code interface presents file and terminal proposals for approval.
UNDER THE HOOD
Explore the architecture.
Trace the components.
Select a node for its role in the system.
Trace connections 9 relationships
- Angular client→FastAPI backend
- VS Code sidebar→FastAPI backend
- FastAPI backend→SQLite persistence
- FastAPI backend→Registered workspace tools
- FastAPI backend→Ollama local model
- Ollama local model→FastAPI backendtool loop
- FastAPI backend→Change or command proposal
- Change or command proposal→VS Code approval
- VS Code approval→Registered workspace toolsapproved action
Select a component to see how it fits into the system.
CAPABILITIES
What’s inside.
- 01
Streaming chat and persistent, searchable conversation history
- 02
Repository browsing, ripgrep search, file previews, Git status and diffs
- 03
Ask and Agent modes with visible tool activity
- 04
Editor selection, active-file, and diff attachments
- 05
Explicit approval before proposed edits and terminal commands