Issue #1: Where to find everything.
The releases page, the update skill, and how to reach us. Two minutes, and you're oriented.
Welcome to the first MixShift newsletter.
Why now? Because we are building fast. Development moves in quick problem-solving cycles, new surfaces like the Claude Plugin keep shipping, and staying in sync by word of mouth stopped scaling. MixShift exists to enable builders, and this newsletter is how we keep you informed on what is new each week and route what you need back into what we build next.
First things first. This issue is an orientation: where releases live, how to update, and how to reach us. Next issue catches you up on the latest release. After that, every issue assumes you know where things live and gets straight to the good part.
1. The releases page
Everything we ship lands at mixshift.ai/releases, newest first. The current version as of this issue is 0.8.6. Each entry says what was added, what changed, what was fixed, and any practical guidance in plain language, not commit messages.
You can also read it without leaving your session: just ask "what's new with MixShift?" in Claude with the plugin, and you get the same changelog right in the chat.
2. How to update (there is a skill for this)
As of 0.8.6, the plugin tells you at the start of a session when a newer version is available or when it just updated. When that happens, or any time you want to check:
Try this: open Claude with the MixShift plugin and say:
"update the plugin"
The mx-update skill walks you through the exact update steps for your setup (terminal, Claude Code, or Cowork), shows what changed since your version, and offers any recommended follow-up steps one at a time, with your confirmation before anything runs.
One note for teams on org-level installs: when a new release ships, the org-level zip needs to be re-installed via the newest version from the releases page. Personal installs update in place.
3. How to get help and send feedback (skills for this too)
Stuck, lost, or wondering what the plugin can do? Say "help" in a MixShift session. The mx-help skill shows you everything the plugin can do, points you at the right skill for the job, and can run a quick diagnostic when something is not working.
Have a bug, a request, or an opinion? Say "send feedback". The mx-feedback skill confirms your message with you, then delivers it to the MixShift team in real time. As of 0.8.6 this works from every surface, including sandboxed and scheduled runs, so nothing you send gets lost.
And if you would rather just talk to a person: reply to this email. It goes to MixShift, and every reply gets a personal answer. If we already solve your problem, we point you at the skill. If we build it, we ship it with your name on the release note.
Don't have the plugin yet? Get it here.
Next issue: what shipped in 0.8.6 and the one skill to try first.
Talk next week.
The MixShift Team