LevelFive-Studio rebrands Mike as Helix Tribune

A fork puts its own name on the product and the AI assistant - and deliberately stops there.

brandingdrafting

LevelFive-Studio renamed everything a user actually sees: the product title, the sidebar and logo, the support copy, the web domains, and the assistant's own introduction - it now answers to "Helix Tribune" instead of "Mike." What they left untouched is the point. All the internal plumbing keeps its original names, so the team can keep pulling in updates from the original Mike project without the rename turning every future merge into a fight.

One detail worth flagging for anyone who lives in Word: when the assistant proposes edits as tracked changes, the revisions now show up under the author name "Helix Tribune." If you're white-labeling a legal AI tool, that author label is exactly the kind of thing that surfaces to opposing counsel and clients, so it's worth getting right.

So what Anyone planning to white-label an open legal-AI tool should copy this pattern: rebrand the surface, leave the wiring alone, and check what name lands in your tracked changes.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from LevelFive-Studio/helix-tribune, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date

c80a9233 brand: rename product Mike -> Helix Tribune (user-facing strings only) Sarat Pediredla 2026-05-15 ↗ GitHub

SHA	Subject	Author	Date
`c80a9233`	brand: rename product Mike -> Helix Tribune (user-facing strings only)	Sarat Pediredla	2026-05-15	↗ GitHub
commit body Identifiers (mikeApi, MikeChat, MikeIcon, MikeMessage, package names, backend/db/storage docstrings) intentionally still reference "mike" - that's the upstream project name and renaming them across the codebase would be churn without benefit. This commit renames only what an end user can see: - Page <title>, OpenGraph, Twitter card, and metadataBase URL in frontend/src/app/layout.tsx - Global error <title>, sidebar header, site-logo text + landing href - Tabular and workflow column-prompt placeholders, model-settings copy, support form "question" description - LLM system prompts ("You are Mike, ...") in chatTools.ts and routes/tabular.ts so the assistant introduces itself correctly - DOCX tracked-changes author label so edited documents show "Helix Tribune" as the change author in Word - Backend startup log line - README heading + product description + website link - CLAUDE.md product description (with a note that identifiers stay) Domain refs `mikeoss.com` / `app.mikeoss.com` are replaced with `tribune.helix.levelfive.studio` everywhere they're user-facing. The upstream-repo references (`mikeoss/mike`, `willchen96/mike`) in infra/UPSTREAM.md and the README's "fork of" line are deliberately left alone - they correctly point at the upstream we forked from. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

commit body

Identifiers (mikeApi, MikeChat, MikeIcon, MikeMessage, package names,
backend/db/storage docstrings) intentionally still reference "mike" -
that's the upstream project name and renaming them across the codebase
would be churn without benefit. This commit renames only what an end
user can see:

- Page <title>, OpenGraph, Twitter card, and metadataBase URL in
  frontend/src/app/layout.tsx
- Global error <title>, sidebar header, site-logo text + landing href
- Tabular and workflow column-prompt placeholders, model-settings
  copy, support form "question" description
- LLM system prompts ("You are Mike, ...") in chatTools.ts and
  routes/tabular.ts so the assistant introduces itself correctly
- DOCX tracked-changes author label so edited documents show
  "Helix Tribune" as the change author in Word
- Backend startup log line
- README heading + product description + website link
- CLAUDE.md product description (with a note that identifiers stay)

Domain refs `mikeoss.com` / `app.mikeoss.com` are replaced with
`tribune.helix.levelfive.studio` everywhere they're user-facing. The
upstream-repo references (`mikeoss/mike`, `willchen96/mike`) in
infra/UPSTREAM.md and the README's "fork of" line are deliberately
left alone - they correctly point at the upstream we forked from.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-436.md from inside the repo you want the changes in.

⬇ Download capture-thread-436.md