Pare 0.1.5

A short release on top of 0.1.4, about coming back to work you did not watch
happen — and one keystroke that should have been this way all along.

New

• Enter sends. Pressing ↵ now sends from every text box in the app, the
  welcome screen included. ⇧↵ makes a new line, and ⌘↵ still sends if
  that is the habit you have. Until now the chat bar wanted ⌘↵ and the welcome
  screen wanted ↵, which was nobody's idea of a feature.
• See what happened while you were gone. Open a project and any changes you
  have not looked at yet are waiting at the top of the Agents panel: how many,
  how they turned out, and one row each with what Pare said it did and how many
  lines moved. A change you sat and watched land does not show up — this is for
  work that happened without you.
• A picture with each one. Where Pare took a screenshot to check its own
  work, that frame is kept and shown beside the change, so you can see what
  landed without opening the project up. Off if you have turned the visual check
  off in Settings, and the picture is only ever stored on your Mac.

---

Apple silicon only. Updates install themselves — you should not need to download
this again.

Pare 0.1.4

A small release on top of 0.1.3, about staying in control of a queue that works
on its own.

New

• Pare stops at milestones. Set to keep going, it now pauses when it reaches
  a natural boundary rather than working straight through the list — and the
  banner offers Undo it, which puts back everything from that stretch in one
  go, not one change at a time.
• Suggestions, not surprises. While it works, Pare can notice something
  worth doing later and propose it, with a reason attached. Suggested items sit
  in their own section and never run until you accept one.
• What you type goes next. A request typed into the chat now jumps ahead of
  anything you did not compose yourself, instead of landing at the back of the
  queue.

---

Apple silicon only. Updates install themselves — you should not need to download
this again.

Pare 0.1.3

Three and a half weeks of work since 0.1.2, and one fix that matters more than the rest.

Fixed: templates would not open

Next.js 16 made Turbopack the default, which ignores the hook Pare injects to map
elements back to source — and then refuses to start at all. On top of that, a race
meant Pare could launch the dev server twice for one project, the first time without
instrumentation. Between them, opening a template usually failed. Both fixed.

New

• Several projects at once. Tabs are workspaces now — open two projects side by
  side, each with its own preview, dev server and agents.
• A backlog that survives quitting. Queue work, close Pare, come back to it. A
  freshly scaffolded project arrives with a roadmap and a few suggested next steps,
  held until you say go.
• Restore points. Set one, make ten changes, put it all back.
• One at a time, or keep going. Choose whether Pare pauses after each item for you
  to look, or works down the list on its own. It pauses by default.
• A build charter. Pare reads a project the first time you open it and writes down
  what the product is, then keeps notes on decisions as it works. Readable and
  deletable from the project menu.
• Voice input, a redesigned composer, a searchable template gallery with
  screenshots, project thumbnails on the home screen, and a proper Settings window.

Also

Markdown rendering for Claude's replies, a reachable zoom reset, and a security
advisory closed in a shipped dependency.

---

Apple silicon only. Updates install themselves — you should not need to download
this again.

Pare 0.1.2

Internal test build of Pare for macOS (Apple silicon).

Fixes both bugs found while testing 0.1.1 on a second Mac.

Fixed

• Voice input now works in a packaged build. The Info.plist usage
  descriptions were being written into the bundle as a nested array instead
  of top-level keys, so macOS never saw them and voice reported
  "this build is missing its speech-recognition usage description."
  This affected every packaged build ever made.
• Creating a new project no longer fails with npm install exited with code 127. A Mac app launched from Finder gets a minimal PATH that does
  not include Homebrew, so npm could not be found. The dev-server path
  already handled this; the scaffolder did not. Opening an existing project
  was unaffected, which is why this hid for so long.

Also

• The build harness now reads the built Info.plist rather than the config
  file, so this class of bug fails on the build machine instead of on a
  tester's.

Pare 0.1.1

Internal test build of Pare for macOS (Apple silicon).

Signed with Developer ID, notarized by Apple, and stapled.

Install: download pare-0.1.1.dmg, open it, drag Pare to Applications.
You will need an Anthropic API key on first run (Settings → API key).

Since 0.1.0

• Voice — dictation waveform and the ⌥ hold gesture, plus four silent
  bugs removed, including a microphone race that could make a recording
  session capture nothing at all.
• Dictated text is tidied before it lands in the chat box.
• Diagnostics — a local log ring, a crash breadcrumb, and a
  "Report a problem" flow. Nothing is transmitted; a report is only ever
  shared by hand.

If you installed 0.1.0, the app should offer this build automatically.

Pare 0.1.0

Internal test build of Pare for macOS (Apple silicon).

Signed with Developer ID, notarized by Apple, and stapled — Gatekeeper
should accept it from a normal download with no right-click-to-open dance.

Install: download pare-0.1.0.dmg, open it, drag Pare to Applications.

You will need an Anthropic API key on first run (Settings → API key).

Built from d40ad86 (slice 89). Note this build predates the slice 106
voice fixes — if you are testing dictation, update to 0.1.1.