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/exittyped 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