SeaShell can keep your code private by building its codebase index with local Ollama embeddings, so source is never sent to a third-party service. You still get hybrid semantic and keyword search, and the index is stored outside the repository and keyed per project in 2026.
Why local embeddings matter
Semantic code search normally sends code to an embedding service. SeaShell can run embeddings locally with Ollama instead, so your source never leaves your machine while still being searchable by meaning.
For teams under privacy or compliance constraints, that distinction is decisive. You get the benefits of meaning-aware retrieval, hybrid semantic and keyword search fused by reciprocal rank fusion, without shipping proprietary code to an external provider.
How SeaShell stores the index
SeaShell keeps the code index outside the indexed repository, keyed per project, so it never pollutes your working tree. Indexing is incremental and hash-keyed, so only changed files are re-embedded.
Keeping the index out of the repo means no accidental commits of index data and clean separation per project. Incremental indexing keeps it fast: editing a file re-embeds just that file, not the whole codebase, so search stays current with low overhead.
On your machine, permission-gated by design
When you run a local embedder (Ollama), your code is read, chunked, embedded, and stored on your own machine. There is no embedding service in the path, so there is no third-party copy of your source to worry about.
Combined with permission-gated tools, that gives security-conscious teams a clear story: the code path stays on hardware you control, and every tool call the agent makes is checked against allow, ask, and deny rules before it runs. Privacy here is a property of where the data physically goes, not a retention promise you have to take on faith.
Frequently asked questions
- Can SeaShell keep my code private?
- Yes. SeaShell can build its code index with local Ollama embeddings, so source code is never sent to third-party servers.
- Do I lose semantic search if I run locally?
- No. Local embeddings still power hybrid semantic and keyword search, so you keep meaning-aware retrieval.
- Where is the code index stored?
- Outside the indexed repository, keyed per project, and updated incrementally so only changed files are re-embedded.
- Does indexing call an external service?
- No. With local Ollama embeddings, indexing runs entirely on your machine, so no embedding provider ever sees your code.
Try SeaShell in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install SeaShellRelated guides
Atlas with Snowflake Cortex in 2026
Explore Atlas with Snowflake Cortex in 2026. Access frontier models like Claude Opus 4.8 and GPT-5.5 within your Snowflake security boundary, billed in credits.
Atlas with Command R7B in 2026
Explore Atlas with Cohere's Command R7B, a cost-effective model for coding tasks in 2026. Leverage its 128,000 token context window for efficient code indexing and planning.
Atlas with Qwen3 Coder Plus in 2026
Atlas with Qwen3 Coder Plus in 2026: Harness its 1M token context and $1/Mtok input for agentic coding. Understand its prose limitations and $5/Mtok output cost.
Write Unit Tests for Untested Code with Atlas in 2026
How to write unit tests for untested code with Atlas in 2026: the lsp tool enumerates exported symbols, grep copies repo conventions, and bash actually runs the suite.
Atlas for Quarkus in 2026
Atlas is a terminal-native AI coding agent for Quarkus in 2026. It reads CDI beans and JAX-RS resources, then runs ./mvnw test behind a permission prompt.
Atlas with Qwen3 14B in 2026: A Developer's Guide
Evaluate Atlas with Qwen3 14B for your coding agent in 2026. This 14B model offers reasoning capabilities, a 128K token context, and reliable tool use at $0.35/Mtok input.
Atlas with Amazon Bedrock (gateway) in 2026
Drive Atlas with Amazon Bedrock (gateway) in 2026. Access Claude, Llama 4, DeepSeek-R1, Qwen3-Coder, and Nova models behind a single AWS IAM boundary, offering up to a 3.5M token context window and passthrough AWS rates.
Atlas with Claude Sonnet 4.5 in 2026: A Developer's Guide
In 2026, Atlas developers can leverage Claude Sonnet 4.5 for large codebase understanding and multi-file edits. Explore its 1M token context and $3/$15 pricing.