Search, inspect, edit, validate, and review inside your working tree.
Code faster. Stay in control.
StemCode is GrowBitLabs' local-first AI coding agent for desktop, terminal, VS Code, Visual Studio, JetBrains, and CI code review. It works inside a real repository, uses real tools, and keeps you in control of what runs.
npm install -g stemcode
Profiles, permissions, approvals, tracked edits, undo, and redo.
CLI, desktop, editors, ACP integrations, and CI review automation.
███████╗ ████████╗ ███████╗ ███╗ ███╗ ██████╗ ██████╗ ██████╗ ███████╗ ██╔════╝ ╚══██╔══╝ ██╔════╝ ████╗ ████║ ██╔════╝ ██╔═══██╗ ██╔══██╗ ██╔════╝ ███████╗ ██║ █████╗ ██╔████╔██║ ██║ ██║ ██║ ██║ ██║ █████╗ ╚════██║ ██║ ██╔══╝ ██║╚██╔╝██║ ██║ ██║ ██║ ██║ ██║ ██╔══╝ ███████║ ██║ ███████╗ ██║ ╚═╝ ██║ ╚██████╗ ╚██████╔╝ ██████╔╝ ███████╗ ╚══════╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═════╝ ╚═════╝ ╚══════╝
I need to wire the worker host and verify the health endpoint before the next run.
• click to collapsebuilder.Services.AddHostedService<Worker>();builder.Services.AddSingleton<IMetricsClient, MetricsClient>();var app = builder.Build();app.MapGet("/health", () => Results.Ok("ok"));app.Run();builder.Services.AddHealthChecks();builder.Services.AddHttpClient<IMetricsClient, MetricsClient>(client =>client.BaseAddress = new Uri(builder.Configuration["Metrics:BaseUrl"]!));builder.Services.AddHostedService<Worker>();var app = builder.Build();app.MapHealthChecks("/healthz");app.Run();Patch is in. Reading the bootstrap file and checking the build output.
• click to collapse! and quickly rerun or expand commands using
!!.
.stemcode/
files.
Built for practical engineering work, not a detached chat sandbox.
StemCode can understand unfamiliar code, create implementation plans, edit files, run checks, review diffs, and automate pull-request feedback while preserving local control.
Understand
Repository-aware search, file inspection, summaries, symbols, definitions, references, and diagnostics.
Plan
Turn feature requests and bugs into concrete implementation steps before making changes.
Edit & validate
Apply tracked edits, run real shell tools, execute checks, and iterate without leaving the working tree.
Review
Review local diffs, files, pull requests, and merge requests with a findings-first workflow.
LSP-powered code intelligence
Symbols, definitions, references, diagnostics, and rename previews are built into the agent workflow.
Subagents
Delegate focused tasks into independent contexts so the main conversation stays cleaner.
Local voice dictation
Use voice input locally when typing is not the best interaction for the moment.
Shell-first workflows
Run foreground and background terminal commands directly, with path autocomplete for files and directories.
Use StemCode where engineering already happens.
The same agent experience is designed to move between interactive development, editor workflows, desktop work, and automated code review.
Desktop
Chat, model controls, profile switching, activity output, permission prompts, and undo/redo.
CLI
Keyboard-first sessions, one-shot prompts, piped input, quick reviews, and automation-friendly output.
VS Code
Selected-context prompts, file and diff review, chat, and applying suggestions without leaving the editor.
Visual Studio
A docked StemCode tool window powered by the local CLI through ACP.
JetBrains
An IntelliJ-based IDE tool window using the same local CLI and ACP integration model.
CI reviews
Run automated review workflows in GitHub Actions, GitLab CI, and Bitbucket Pipelines.
Build the missing pieces of your AI stack.
Use GrowBitLabs for one specialized layer or for the whole system, from prototype through private production deployment.
Self-hosted LLM systems
Private model deployment, inference APIs, routing, authentication, observability, and operational architecture.
Custom fine-tuning
Adapt models to approved datasets, domains, structured tasks, and organization-specific workflows.
Private RAG
Connect internal files, documentation, databases, and knowledge systems to grounded AI workflows.
Edge AI
Optimize and deploy models to laptops, workstations, embedded computers, and offline systems.
Custom agent integration
Extend workflows with internal tools, MCP servers, CI systems, policies, and organization-specific automation.
Private AI product engineering
Design the full product path from application UX through agents, model routing, data, and infrastructure.
AI should become
infrastructure,
not dependency.
The model will change. The API will change. Your product should not have to start over every time it does.
Useful automation without silent surprises.
StemCode makes control visible: profiles separate different kinds of work, permissions define what can run, and sensitive actions can require explicit approval.
Allow, ask, or deny.
Control file edits, shell commands, network access, MCP tools, memory writes, and elevated operations.
Different modes for different work.
Separate implementation, planning, review, exploration, and delegated work.
Undo and redo agent changes.
Tracked edits include whole-file writes, patches, insertions, and targeted search/replace operations.
Project knowledge you can review.
Store repeatable commands in .stemcode/commands and long-lived context in .stemcode/memory.
Private AI, without the vague answers.
Is StemCode a GrowBitLabs product?
Yes. This site presents StemCode as the coding-agent product from GrowBitLabs, while GrowBitLabs also offers broader private AI infrastructure and engineering services.
Does StemCode require one specific AI provider?
No. It supports multiple hosted providers, subscription-style sign-in, OpenAI-compatible endpoints, and local model setups including Ollama and LM Studio.
Can StemCode run in CI?
Yes. It supports automated review workflows for GitHub Actions, GitLab CI, and Bitbucket Pipelines.
Can GrowBitLabs help us deploy private models for StemCode?
That is a natural fit for the broader GrowBitLabs service offering: local, VPC, on-prem, or other private model infrastructure can be designed around your workflow.
Bring us the hard AI problem.
Tell us what you want to build, what needs to stay local, which development surfaces matter, and where your models should run.