zevra-tech/mikeoss-test

An early-stage zevra-tech fork of Mike focused on smoothing out the contributor setup story.

Early days - a single thread of work landed just before we first saw the fork, with no broader roadmap visible yet.

View on GitHub →

This is zevra-tech's fork of Mike, and at the moment it's barely diverged from upstream. The one visible thread of work is about developer environment plumbing - making it easier to spin up a working copy of Mike inside a containerized dev setup wired to Claude Code.

There's no product pivot here yet, no rebrand, and no signal about a particular legal niche. If you tried this fork today, you'd essentially get Mike, with the difference being felt by whoever is checking out the code rather than by an end user.

What zevra-tech is signalling, instead, is interest in the contributor experience. That's a reasonable foundation to build on, but the direction beyond "make it easier to hack on" isn't visible yet. Worth a click through if you're curious about their dev setup; not yet worth one if you're shopping for a differentiated Mike variant.

What's in it

Direction

infrastructure

Activity

Themed changes and pull requests touching this fork, newest first. Themed changes that haven't been turned into a public post yet still appear — they're real work even without a published writeup.

📝 Devcontainer for Node.js + Claude Code (no public page) 1 commit 7d ago not yet rewritten