[jerelvelarde]

The problem

OpenDuet already says at the top that it is built on OpenBot, but not what that means for the person reading. Nothing says that OpenDuet also ships inside OpenBot as a skin, that OpenBot is the version CopilotKit maintains, or where to go to run it for a team instead of copying the folder. Further down, the README still calls OpenDuet "in active development" and "built and maintained by CopilotKit", which is no longer true now that it is community maintained.

#97 answers this by opening the README with a notice that OpenDuet now lives in OpenBot. That is accurate about where the maintained code is, but it sits above the name, the description and the demo, so the first thing a visitor reads is that the project has moved on. This repo still brings people in on its own, and a header that sends them away before they have seen what OpenDuet does risks losing them for OpenBot as well.

The approach

The header stays OpenDuet's. The name, description, badges, Trendshift badge and demo are where they were, and OpenBot comes in at three points.

A lead line and a screenshot of OpenBot. "OpenDuet is now available as a UX skin in OpenBot, a more robust version with sign-in, per-Bot permissions and an audit trail, maintained by CopilotKit. This repo stays a community-maintained starter for building your own project." Under it is OpenBot itself running the OpenDuet skin, linked to OpenBot. The picture does the explaining: it is recognisably OpenDuet, and it is OpenBot. The image is committed as docs/images/openbot-openduet-skin.png so it does not depend on an attachment URL.

The call link now reads "Bringing OpenDuet to your company? Talk to us about OpenBot" and keeps its ref=openduet_readme tag, so its conversions compare directly with before.

An "OpenDuet and OpenBot" section right after the demo video, before Overview. A three-row table sends someone who wants to try OpenDuet or make it their own to this repo, someone who wants to run it for a team, with sign-in, per-Bot permissions and an audit trail, to OpenBot and its Skin setting, and someone who wants it stood up for them to an engineer. It ends by saying which repos are community maintained and which one the CopilotKit team ships fixes to. Its call link carries a new tag, ref=openduet_readme_openbot, so traffic from the section can be told apart from the header.

Two wording fixes. "Early, and in active development." becomes "Early.", and the About line changes from "built and maintained by CopilotKit" to "built by CopilotKit and is community maintained", so the page agrees with the lead line.

The cost is that the screenshot pushes OpenDuet's own demo further down the first screen. That is the trade this version makes on purpose: a reader who stops at the first screen now sees OpenBot, and sees it as something they already recognise.

What is not covered

• Only the top of the README changes. Later sections still describe the repo on its own terms.
• The screenshot is OpenBot main at 72709c5, run locally in single-user mode with the two default Bots and four seeded chats. It is a still, so it goes stale when OpenBot's home screen changes, and it shows the empty composer rather than a conversation, because a conversation needs a live model and Intelligence project.
• The Settings → Skin path is OpenBot's current interface. If the setting moves, the caption and the routing table go stale.
• The same change is open for OpenDots in Lead with OpenDots as a skin in OpenBot, and show it OpenDots#186 and OpenMuse in Lead with OpenMuse as a skin in OpenBot, and show it openmuse#220.

Verification

• The screenshots above are GitHub's own rendering of this branch's README, captured from the branch page.
• The OpenBot image was captured from OpenBot main (72709c5) with the skin set on the account through PATCH /api/settings/preferences, and the page's data-skin attribute confirmed it drew that skin.
• All 16 in-page links on the branch resolve to a heading in GitHub's render, and OpenBot#quick-start exists in OpenBot's README.
• Every new outbound link returns 200: OpenBot, the two sibling repos, and both talk-to-an-engineer links.
• CI's format check runs Biome inside openbot/, so the README at the repository root has no format gate.
• The diff is README.md and docs/images/openbot-openduet-skin.png, in two commits on top of main.

Merge notes

This is an alternative to #97. Both rewrite the top of README.md, so whichever merges, the other should be closed rather than rebased.