Pyre v0.2.0 — talk lane

Two additions since v0.1.0.

Talk lane — say > to the AI

Type a line starting with > in the bar and it becomes a message to whatever agent is connected over MCP, not a note:

> move winwater to friday and bank the invoice till tomorrow

It appears in a lane under the composer. The agent reads it with the new list_messages tool and answers with send_message; the reply lands in the lane and the TALK button carries an unread count. > outranks the rest of the grammar, so a message can contain slashes freely.

Messages ride in the same notes.json under an optional messages array, so the existing file watcher delivers replies with no extra plumbing — and a file without the key stays perfectly valid. They are not notes: no deadline, no burn, no grid cell.

The lane is pull-based. Nothing pushes a message to your agent; it sees one when it calls list_messages. Ask it to check Pyre, or tell it to poll at the start of a session.

Reserve screen space

The setting that was previously stored but did nothing now works. Turning it on registers the rail as a Windows AppBar, so maximised windows stop at its edge instead of hiding behind it — the way the taskbar behaves. Verified against the live work area, and released cleanly when you turn it off or quit.

It is off by default, and the whole FFI path is guarded: if it cannot load, the setting simply does nothing rather than blocking startup.

Also

• quit / exit typed in the bar closes the app (v0.1.x had tray-only).
• 63 tests, up from 51.

Downloads

File	Use it when
Pyre-Setup-0.2.0.exe	You want a Start Menu entry. Per-user, no admin. Full MCP support.
Pyre-0.2.0-win.zip	Portable, self-contained. Unzip anywhere; add an empty pyre.portable file beside Pyre.exe to keep notes in the folder. Full MCP support.
Pyre.exe	Single file, double-click, nothing installed. Its launcher can't pass stdio through, so use the built-in local HTTP MCP endpoint.

Unsigned, so SmartScreen warns on first run: More info → Run anyway.

Setup and MCP configs: README

Pyre v0.1.0

A frameless, transparent, always-on-top rail of square paper notes. A note with a deadline burns away from its bottom edge in its last two hours — you glance at the edge of your monitor and know, without reading a word, what is about to burn you.

Which download?

File	Use it when
Pyre-Setup-0.1.0.exe	You want a Start Menu entry. Per-user, no admin. Full MCP support.
Pyre-0.1.0-win.zip	Portable, self-contained. Unzip anywhere, add an empty pyre.portable file next to Pyre.exe to keep notes in the same folder. Full MCP support.
Pyre.exe	Single file, double-click, nothing installed. Note: its launcher can't pass stdio through, so stdio MCP is unavailable — the built-in local HTTP endpoint works fine.

Unsigned, so SmartScreen will warn on first run: More info → Run anyway.

What it does

• The fuse. Nothing burns until T−2h; the front then climbs on an ease-in curve, maxing at the deadline and capping at 30% so the note stays readable. A separate ambient warmth ramps over the last 24h.
• Your hand beats the sort. Auto notes sort hottest-to-top-left. Drag one and it holds that cell forever — fire flows around it rather than evicting it. If a pinned note catches fire below the fold, an ember pip points at it instead of moving anything.
• One-line capture. topic / comment / due, with fri 9am, 3d, 8/21 3pm, tomorrow. Live chips always show the resolved date, so fri can never quietly mean the wrong Friday.
• Agent-readable. One notes.json, atomically written and watched — edit it from anything and the wall animates the change in. Ten MCP tools over stdio (Pyre.exe --mcp) or a loopback HTTP endpoint, for Claude Desktop, Claude Code and Cursor. The agent and the screen share one burn curve, so they can never disagree.
• Achromatic paper and light throughout — fire is the only chroma in the product.

Full setup, keybindings and MCP configs: README