Skip to content

Stet 0.3.1

Choose a tag to compare

@rainesdrew rainesdrew released this 29 May 20:50
1c992f8

Added

  • Native macOS menu bar. File / Edit / View / Window / Help with Open Folder, Open Recent (last 10), Open the Demo Workspace, and Open in AI Agent (Claude Code, Cursor, VS Code/Cline) — all available without clicking into the editor header.
  • Local proposal intake. Coding agents running on your machine (Claude Code etc.) can now edit files directly — Stet's filesystem watcher captures every external write as a reviewable proposal on a rolling local/proposals branch. No more agent edits silently bypassing the review flow.
  • HTML annotate mode. Stet now opens .html files alongside markdown, with the same diff and proposal pipeline.
  • Feedback hub. The floating feedback bubble now opens a three-option hub: send feedback (screenshot + text, as before), join the Stet community on Discord, or book a 15-min call with Drew. Discord replaces the opaque single form with a place where testers can see each other's reports.
  • Discord integration on the feedback receiver. Every submitted entry is also posted to the Stet Discord channel as a rich embed with the screenshot attached, so feedback lands somewhere visible immediately.

Changed

  • Agents see your latest edits. The editor now writes to disk on every change, so when a coding agent reads a file, it gets your in-progress content instead of a stale on-disk snapshot.
  • CLAUDE.md offer banner refreshed — narrower layout, clearer copy, and updated guidance for local vs remote agents.
  • Demo workspace docs updated to reflect the new local-intake flow.

Fixed

  • AI note (✦) resolutions now produce a proposal pill correctly, including across multi-hunk changes. Hunk merging tolerates overlapping ranges, and stripMarkdown no longer mangles certain inline-code patterns.
  • The inline preview for a pure-insertion change no longer renders the surrounding context line as if it were part of the new content.
  • The rolling local/proposals branch now diffs against the home-branch tip instead of merge-base — without this fix, already-accepted local proposals leaked back into later proposals and broke AI-note resolution classification.

Internal

  • Vitest setup (jsdom + Testing Library) with initial frontend unit tests for Toolbar, diff, and recentWorkspaces; npm test runs both Vitest and cargo test.
  • Rust unit tests for fs_ops and proposal_intake; tempfile added as a Cargo dev-dependency.
  • E2E harness scaffolding under e2e/.