Applications are interactive tools that live directly inside your workspace — not in a separate tab, not in a linked product, but right there between your paragraphs, alongside your writing and your Charms.

CharmIQ comes with a set of built-in Applications out of the box: Kanban boards, mind maps, note boards, drawing tools, daily task trackers, smart quizzes. Drop any of them into your document and they work immediately.

 is a fully interactive tool you or your Charm builds specifically for your problem. It runs inside your workspace, reads and writes data that lives in the document and connects to the same context your Charms already see. It's not a plugin you install — it's something you create, in your workspace, for exactly the job at hand.

A dashboard that reads your Google Analytics data. A form that writes structured records your Charm can analyze. A code editor with syntax highlighting. A live data pipeline connecting an external API to a Charm-powered analysis engine. Any of these can live in a CharmIQ document, right next to the thinking that produced them.

Most tools that embed "widgets" are giving you a view into a separate system. The widget and the document are strangers — they share screen space but nothing else.

CharmIQ Applications are different. They share the same data layer as everything else in the document. An Application can write data that a Charm reads. A Charm can generate content that an Application renders. Two Applications in the same document can discover each other and pass data between them in real time. Multiple people can edit the same Application's data simultaneously — changes merge safely, just like collaborative text editing.

 Your Applications, your Charms, your writing, your slides — all of it operates on the same content, in the same space.

Applications have the same connectivity as Charms. That means:

 — An Application can authenticate with Google, GitHub, Microsoft, Slack, and dozens of other providers. A dashboard that reads your Analytics data doesn't need a separate login flow — it connects through the same OAuth infrastructure that powers your Charm integrations.

 — Applications can call MCP servers directly. If your Organization has connected a data warehouse, a code repository or a Zapier workflow, your Application can reach it.

 — Applications in the same document can discover each other and communicate. One Application captures data; another visualizes it; a third logs the results. Each one focused on its job, all of them collaborating in the same workspace.

And best part is: you don't write the code. Your Charm does.

"I want a form that collects structured project notes and stores them so you can analyze them later"

 — and your Charm builds it. For a simple tool, that's a single-file HTML Application that appears in your document immediately. For something more complex, your Charm can scaffold an entire folder-based Application with multiple components, write the files and produce a working tool in one pass.

The developer documentation that follows exists for two audiences: developers who want to build Applications themselves and Charms who need to know the full range of what's possible so they can build it for you.

If you're not writing code yourself, you don't need to read further. Tag your Charm, describe your tool, and let it build.

 — How Applications are built, from a single HTML file to a full folder-based project.

 — How Applications store and share data inside the document.

Interactive tools that live inside your workspace — built-in or custom-built for exactly the job at hand.

What is an Application?

Not a Widget. Not a Plugin.

What Makes This Different

What Applications Can Connect To

You Don't Need to Build It Yourself

Next Steps