Ember Console from Claude: the same report, built from a different AI

Ember Console is a session-report builder for coaches, in closed beta, and it runs from whichever AI you already use. Change from ChatGPT to Claude and the report is still built to your template. Four things set its shape, and all four stay in Ember: your letterhead, your boxes, the prompt in each box, and the standard each box has to pass.

I call those four the handover set, because Ember hands them over on every build. Claude is one of three AIs named on Ember’s landing page, which says Ember stays “accessible directly from ChatGPT, Claude, or Littlebird”.

What stays the same when you change AI?

All four parts of the handover set, because not one of them lives in the model.

1. Your letterhead, which every plan keeps.
2. The boxes your template is cut into.
3. The prompt inside each box.
4. The eval that box has to pass.

Every time an AI fills and builds the report it receives all of those prompts and the eval system, and it reworks each box until the box clears your minimum standard. So a model swap reaches the prose and stops there. A different AI writes different sentences inside box three, and the eval on box three decides whether they stay.

The box system is where one box gets cut. The prompt for session notes is the longer answer on what the eval takes off the prompt.

Where should your report standard live?

In the template, the one place you edit on purpose.

The question is live well outside coaching. A retired bookkeeper cleaning up the accounts of several nonprofits at once asked r/ClaudeAI where to keep what. One reply drew the line like this: “memory = how to work with you, project/context = what this particular client situation contains”.

A report standard sits badly in either of those, because it has to read the same on report four as on report one. Another r/ClaudeAI thread, 161 points and 73 comments, is one poster’s account of finding a memory setting already on across their projects, then losing an hour to sorting out what had crossed between them.

A pass mark should not sit anywhere you have to go and check. In Ember it is a line you wrote inside a box, and the next build gets it whichever AI does the writing.

So if you do change AI, build one report on the new one, same template and same kind of session, and read it against the last report from the old one. The template did not move, so anything different is prose, and anything the eval let through is a line you can tighten.

What is not stated yet?

Three things about reaching Ember from Claude, and I have not written down any of them.

1. Whether you reach Ember from Claude by a connector, a project, or a skill.
2. What you do inside Claude to start a report.
3. Which Claude plan is needed, if any.

So take no mechanics from this page, or from anyone else’s. Ask me, and the answer goes here once it exists.

Decide the pass mark first, because the AI writing to it is the one part you can change on a Tuesday without rewriting anything.

Questions people ask next?

Does Ember Console work with Claude?

Ember Console is callable by any local or cloud AI, and the landing page names three of them: ChatGPT, Claude and Littlebird. It is in closed beta, and how a coach reaches it from Claude is not stated yet.

Do I have to rebuild my template for each AI?

No. The letterhead, the boxes, the box prompts and the evals sit in Ember, and the AI that builds the report receives them each time. Changing which AI writes does not change the template it writes into.

Which Claude plan do I need for Ember Console?

Not stated yet, so do not plan around an answer. The Ember pricing page states only what holds across its three plans: “Every plan keeps your letterhead, exports to PDF or Word, and your data stays yours.”