There’s no shortage of developer platforms. Dashboards, SaaS products, browser extensions — each adding another tab, another login, another subscription. We went a different direction.

Pioneers builds CLI tools. Here’s why.

Four principles: Terminal-first, Composable, Local-first, Open Source — connected to Pioneers CLI Tools

The Terminal Is Already Open

Developers live in the terminal. Git, npm, pip, docker, kubectl — the tools that actually ship software are all command-line programs. A CLI doesn’t interrupt your flow. It fits into the environment you’re already working in.

When we built code-explore, the goal wasn’t “create a web app for searching projects.” It was: make cex search "auth middleware" return the right project in under a second, right where you’re already working.

Composability Over Features

A CLI with --json output is infinitely more flexible than a dashboard. You can pipe it, script it, cron it, integrate it into CI. Every command in code-adapt and code-explore supports --json for exactly this reason.

Want to observe upstream changes and post a summary to Slack every Monday? That’s a three-line shell script, not a feature request.

cadp observe my-upstream --since 7d --json | \
  jq '.observations | length' | \
  xargs -I {} curl -X POST "$SLACK_WEBHOOK" -d "{\"text\": \"{} upstream changes this week\"}"

No webhook configuration UI. No integration marketplace. Just pipes.

Local-First, No Lock-In

Both our tools store state as plain files — YAML, JSON, SQLite — in your project directory or home folder. There’s no cloud service, no account, no API key required for core functionality.

code-explore’s AI features use Ollama, which runs locally on your machine. Your code metadata never leaves your laptop. If you stop using our tools, your data is still there in readable formats.

Open Source as a Baseline

Every line of code we write ships under MIT. Not “open core” with essential features behind a paywall. Not “source available” with a restrictive license. MIT — use it, fork it, vendor it, we don’t care.

We think the best developer tools earn adoption through utility, not lock-in.

What We’re Building

Two tools, one philosophy:

code-explore — Scan all your projects, build a searchable knowledge base with AI summaries, find anything with hybrid fulltext + semantic search.

code-adapt — Track upstream repository changes, assess their relevance, plan and implement adaptations, contribute back.

Both are Python CLIs, installable via pip, designed to work together. The plan is for code-adapt to use code-explore’s index to understand cross-project impact when assessing upstream changes.

Get Involved

We’re a small team building tools we want to use ourselves. If that resonates:

  • Star or fork on GitHub
  • Open an issue if something’s broken or missing
  • Send a PR — the codebases are deliberately small and readable

The best developer tools are built by developers who feel the pain. We do.