Invent a syntax — any syntax, any file extension. Press ▶ Run and a model reads your imagination the way a compiler reads source, then builds a real, working website.
there are no syntax errors in imagination.
There is no parser to satisfy and no keyword list to memorise. You describe what you mean; the compiler reads intent and writes real HTML or React.
Make a file. Call it .dream, .jasminko, .anything.
Write sentences, curly braces, arrows, invented verbs — whatever feels right to you.
The Imagine Terminal streams the compiler's reasoning as it happens — what it read, how it interpreted each construct, what it built.
Not a mock-up. Actual HTML, CSS and JavaScript served from
/preview/, ready to open, ship or keep imagining at.
.dream filesThese ship with every install. One is written in plain English sentences; the other is a curly-brace language no compiler on earth accepts. This one does.
// synthwave.dreamjs
// an invented curly-brace language.
// no compiler on earth accepts this.
// this one does.
universe SYNTHWAVE {
vibe -> neon, night-drive, 1984, slightly wet asphalt
palette -> #05010f base, #ff2e97 hot, #00e5ff cool
font -> a wide geometric sans, a mono for the rest
}
scene Sky {
background = vertical gradient #05010f → #2b0a3d
horizon.line = 1px of #ff2e97, glowing
grid {
perspective = true
animate -> scroll toward the viewer, forever, 6s
}
sun {
slice = 4 horizontal gaps across the lower half
glow = 80px of #ff2e97
float -> up and down, 4s, gentle
}
}
deck Tracklist {
track { "01" | "Chrome Rain" | "3:58" }
track { "02" | "Lighthouse Protocol" | "4:41" }
track { "03" | "Ghost In The Sedan" | "5:12" }
each track {
border-left = 2px #00e5ff
OnHover -> becomes #ff2e97, slides right 6px
OnClick -> the row starts pulsing
}
}
# bean-there.imagine
# a language made of sentences.
# there is no grammar. write what you see.
imagine a page for a small coffee shop.
the mood is: warm, unhurried, a little bit wooden.
the background is the colour of oat milk,
the text is the colour of espresso.
at the very top, a slim bar.
on its left, the words "Bean There"
on its right, three quiet links:
"menu" · "hours" · "find us"
the bar stays stuck to the top when the page scrolls.
below it, a tall opening scene, centered.
a very large line of text: "we open at six."
under it, smaller and softer:
"the good beans go first."
under that, [ see today's menu ] — a rounded
button the colour of espresso.
when someone clicks it, the page glides down.
then the menu.
a heading: "today"
three cards side by side, thin border, generous
whitespace:
card one
"flat white" · "£3.20"
"milk, folded not poured"
card two
"cortado" · "£3.00"
"small, serious, gone in four sips"
when the mouse hovers a card it lifts a few pixels
and its shadow deepens.
on a narrow screen the three cards stack.
Both panes are the real example files that ship in
resources/seed-workspace/ — and the shape of what they compile to.
Monaco, an explorer, tabs, a command palette, quick-open, a status bar with live chips. Everything you expect from an editor — pointed at a language that doesn’t exist.
Only you know that ~> means “fades in over two seconds”
and not “flows into”. Write it down once and the compiler follows your
definitions instead of guessing. Your spec is sent ahead of your source
on every build.
Claude Code, Anthropic, OpenAI or DeepSeek. Bring whichever you already have — you need exactly one.
Watch the build think. Reading, interpreting, writing — streamed live, with token counts and an estimated cost.
One self-contained page, or function components with hooks via CDN. No build step either way.
Never in localStorage, never in the page. A 0600 file
on your disk — or just an environment variable.
The Windows installer carries its own runtime, its own editor and its own CLI. Not even Node is required.
With Claude Code the compiler edits output/ directly, so a second
run is surgical rather than a rewrite.
The one step that changes the output most. A spec has four parts — a name, prose about how your language works, a glossary of constructs, and worked examples the compiler treats as test cases to match.
x ~> y→x fades into y over two secondsuniverse→the page shell — palette, fonts, moodscene A over B→A is layered on top of B, absolutelydeck→a responsive list of rows::→applies styling to the thing on the leftending→a small centered footer lineImagineCode reuses your existing setup. One provider is enough — and ⚡ Connect verifies it with a real round-trip before you build.
output/ directly, so rebuilds are surgicalsk-ant-… keysk-… keysk-… keyThe built-in model lists are a floor, not a ceiling — ↻ models merges
your account’s own /v1/models response on top.
synthwave.dreamjs on the left,
the site it just became on the right.
Free, open source, MIT. No account, no pricing page, no trial. Windows, macOS, or straight from source — every link below does exactly what it says.
ImagineCode-Setup-1.0.0.exe
Per-user install, no administrator prompt. Start menu and desktop shortcuts. Nothing else needed — not even Node.
Download ↓
ImagineCode-1.0.0-arm64.dmg
Drag to Applications and open. Separate images for Apple silicon and Intel — each carries the Claude Code binary built for it. Unsigned, so the first launch is right-click → Open.
Download ↓the same IDE, in your browser
$ git clone https://github.com/b1onix/ImagineCode
$ cd ImagineCode
$ npm install
$ npm run web
→ http://localhost:3333One compiler provider is all you need. Claude Code works with no key to paste; otherwise an Anthropic, OpenAI or DeepSeek key. First launch plays a short introduction — replay it any time from Help → Show Introduction.