v0.1 · open source · MIT

A terminal coding agent
that ships.

OpenSeek is a lightweight, scriptable coding companion that runs in your terminal. Multi-provider routing, 50+ tools, MCP-native, LSP-aware. Plan, Agent, YOLO — pick your appetite for risk.

Get started↵Star on GitHub↗
14
workspace pkgs
50+
built-in tools
100+
slash commands
~/projects/api • bun openseek64 ctx · plan
❯openseek
▌ Plan mode · provider=anthropic · model=claude-opus-4-7
/find"useEffect" --path src/
→ 14 matches across 9 files
editsrc/lib/cache.ts:42
- if (entry.expired) return null
+ if (entry.expired) { metrics.miss(); return null }
/testcache.test.ts
✓ 18 passed · 0 failed · 1.2s
ready for next instruction
What's inside

Built for people who actually live in the terminal.

No 'sign in to continue', no proprietary cloud round-trip, no opinions about your editor. OpenSeek is plumbing, not a product surface.

  • PROVIDERS

    Route across five backends

    OpenAI-compatible, Anthropic, Bedrock, Vertex, Azure. Swap models per task or per session — no rewrites, no lock-in.

  • TOOLS

    50+ tools, batteries included

    File edits, shell, search, fetch, refactor, run/test, git, browser. The toolset matches what real engineers reach for, not what looks good in a demo.

  • COMMANDS

    100+ slash commands

    Discoverable, scriptable, composable. Chain /plan, /test, /commit. Define your own with skills.

  • PROTOCOL

    MCP-native client

    First-class Model Context Protocol — bring your servers, your data, your skills. Plug in once, use everywhere.

  • EDITOR INTEL

    LSP feedback in the loop

    Diagnostics, hovers, references — piped straight to the agent so it sees your project the way your IDE does.

  • RUNTIME

    Headless HTTP/SSE API

    Run as a service. Stream tokens to your CI, your editor, your bot. The TUI is one frontend among many.

Three modes

Pick your appetite for autonomy.

Same agent, three governance levels. Switch on the fly with /plan, /agent, /yolo — or pin one in your config.

MODE / 01Read-only thinking

Plan

Surveys the repo, drafts a plan, suggests edits. Never writes a file. Use it to reason — fast and reversible.

/plan
→ 6-step plan ready
→ 0 files modified
MODE / 02Confirm-on-write

Agent

The default. The agent picks tools, you keep veto on writes, shell, and irreversible ops. The right tradeoff for daily work.

edit src/db.ts
→ approve / deny / diff
✓ applied
MODE / 03Trust the loop

YOLO

Auto-approve everything. Best for CI runs, sandboxes, or nights when you've already pushed once today.

openseek --yolo "ship the migration"
✓ 7 commits · 0 prompts
Multi-provider

Bring your own model. All five lanes, one agent.

Mix providers per task. Cheap model for /plan, frontier for /agent, local for offline. The router is the product.

  • Anthropic
    Claude 4.x · streaming · tool use
  • OpenAI
    GPT-5.x · responses API · function calls
  • Bedrock
    Nova / Claude / Llama via AWS
  • Vertex
    Gemini · MakerSuite · enterprise
  • Azure
    OpenAI on Azure · region pinning
  • OpenAI-compat
    vLLM · llama.cpp · Mikan Cloud · DeepInfra
Install in 60s

Three commands. No accounts. No SaaS round-trip.

You bring your own API key. OpenSeek talks to your provider directly from your machine — your code never passes through our servers because there are no servers.

macOSLinuxWSL2arm64 · x86_64
step01·Install Bun
$ curl -fsSL https://bun.sh/install | bash
Bun ≥ 1.3 is required. Or `brew install oven-sh/bun/bun`.
step02·Install OpenSeek
$ bun install -g openseek
Also available via `npm i -g openseek`.
step03·Launch the TUI
$ openseek
Headless? `openseek serve --http :7531`.
Honest answers

The questions you'd ask anyway.

If something here is misleading, file an issue. We'd rather lose the user than oversell.

  • ?

    How is this different from Claude Code, Aider, or Codex CLI?

    Same shape, different priorities. OpenSeek is provider-neutral by design — no SaaS, no central runtime, no vendor commitments. Bring any of five backends, swap them mid-session, run the agent headlessly behind your own API.

  • ?

    Why Bun instead of Node?

    Bun gives us startup time, native TypeScript, native fetch, and a workspace runner that doesn't need 14 plugins. The TUI is a 14-package monorepo — Bun handles it without ceremony.

  • ?

    Is my code sent to a third party?

    Only to the provider you configure. There is no OpenSeek backend. Your file edits, shell calls, and prompts go from your terminal directly to the LLM endpoint of your choice.

  • ?

    Can I use it in CI?

    Yes — `openseek serve --http` exposes a streaming HTTP/SSE runtime. Pipe a goal in, get a structured event stream out. Run it inside Docker, GitHub Actions, or your own scheduler.

  • ?

    How extensible is it?

    MCP client + skills + custom tools. If you've written tools for Claude Code or Codex CLI, the wiring is familiar. Skills are first-class — the Skills package is one of the 14 workspaces.

  • ?

    What's the license?

    MIT. Fork it, ship it, embed it, sell something built on top of it. Our only ask: tell us what you built.

$ open source · MIT · written in TypeScript

Stop renting your coding agent.
Run it yourself.

Read the source↗$ bun install -g openseek