@@ 00 · changelog @@

What’s new.

Pyor is pre-1.0 and moving fast, so we log progress as honest month-level milestones rather than version numbers. Here’s what’s landed.

@@ This is where every Pyor release gets logged. Want it in your inbox? Email support@pyor.review and we’ll let you know. @@
  1. September 2026

    Saved views, and merging a stack

    • The PR list is now a strip of saved views you own: name a filter set, give it a colour and an icon, and its count is the real count because filters resolve as GitHub search qualifiers instead of over the rows already fetched.
    • Stacked PRs merge from Pyor. GitHub’s stack preview added a merge-async endpoint, the only one that accepts a stack member, and the merge button, status pill and command palette now use it.
    • Assignees, labels and milestone are editable from the PR rail. Jira keys autolink the way github.com does.
    • When Pyor can’t write to a repository, you get one amber notice that says so and a Manage access button, never a control that would fail.
    • The comments inbox shows one row per review thread with a reply count, and a PR opens from the inbox without a second of dead time.
    • Installing Pyor on an organization starts a 30-day trial for everyone in it, no card. An admin can subscribe from Settings at any time; checkout bills right away.
  2. August 2026

    AI that reads your rules

    • Inline review hints read the repo’s own CLAUDE.md or AGENTS.md (root plus every ancestor of a changed file), so a change that breaks a house rule gets flagged and a pattern the repo endorses does not.
    • A chat rail beside the diff: ask about the PR, let the assistant search the whole repository, and see what each answer cost.
    • AI review runs keep going while you navigate, tracked in a runs dock, and every AI route gets a reasoning-effort control.
    • Hints move into a rail beside the diff, and a hint whose code has since moved is greyed out rather than left pointing at nothing.
  3. August 2026

    Moved code, Slack, and what a force-push replaced

    • Code that only moved is highlighted as moved, not as a delete plus an add, with a chip that splits lines in and lines out.
    • Slack messages that reference a PR show up in the Conversation rail, and PRs already posted in Slack are marked in the list.
    • After a force-push, compare what the new head replaced instead of losing the old diff.
    • CI check details open in a modal, with a running job’s steps streamed live. Open any pull request from ⌘K.
    • Pre-PR reviews gain a Source Control mode: staged and unstaged hunks of the same file are separate rows, the way a git client shows them (desktop only).
  4. July 2026

    GitHub stacked PRs, surfaced

    • When a PR is part of a GitHub stack, a navigator in the header shows where it sits in the chain and lets you jump between layers.
    • The merge box leads with the stack: which layer you’re on, how many merged below and wait above, the branch it merges into, and when the layer below has to land first.
    • Per-layer status at a glance: ready, draft, conflicts, behind base, checks failing, or needs review.
    • Pyor reads the stack GitHub tracks. It doesn’t create stacks or run a merge queue.
  5. July 2026

    Read the document, not the diff

    • Markdown files render as documents inside the PR, with Head, Base and a word-level rendered diff, comments anchored to the sentence, and a full-screen viewer for long docs. MDX followed in August.
    • A commit-by-commit review rail, so a re-review costs only the commits since you last looked.
    • Dependency walkthrough ordering: files sorted by their import graph so you read a change in the order it was built, no AI involved. It became the default list order in August.
    • Whole-PR AI grouping with a redesigned rail, and the PR description feeds the grouping as context.
  6. May 2026

    PR lifecycle management

    • Land and manage a PR without dropping to github.com: merge with the repo-allowed method, optional commit-message edit, and delete-branch.
    • Close / reopen, toggle draft, update-branch, and enable or disable auto-merge: each confirmed before it fires.
    • Request, re-request, and remove reviewers, and dismiss a review with the required reason.
    • Every action is gated by your repository permission, so a control you couldn’t use is never shown.
  7. May 2026

    A home for this changelog

    • Launched the new marketing site: the same diff-shaped surface you review in, on the web.
    • This page is where releases get logged from here on out.
  8. April 2026

    Pre-PR / Local Reviews

    • Review a branch before a PR exists: your own work, or one an agent just handed you (desktop only).
    • See the committed diff against your base alongside a live bucket of uncommitted changes, both updating as you edit.
    • Leave private review notes that never touch GitHub, then export them as a single file to hand to an LLM coding agent.
    • Local reviews are persistent and worktree-rooted: a repo can host several at once, each on its own branch, surviving restarts.
  9. March 2026

    The Comments tab

    • A dedicated Inbox feed of the comments people wrote at you: inline, file, review-summary, discussion, and commit comments, normalized into one shape.
    • Sourced independently of notifications, so a comment that never notified you still shows up, and one that did can still read as unread.
    • Each row carries the body, author, reactions, and the diff hunk for inline reviews.
  10. February 2026

    Viewed state, down to folders

    • Mark files viewed with bidirectional sync to GitHub: GitHub stays the source of truth across machines.
    • Mark whole folders viewed for collapse in the file rail, something github.com doesn’t offer.
    • Viewed state survives refreshes, base-ref updates, and force-pushes; changed content clears it, nothing else.
  11. January 2026

    The first review surface

    • Inbox, Mine, and Participating lenses over your open PRs, with native notifications for new activity.
    • A hybrid layout: familiar top tabs around a three-column Changes pane with rich diffs and a filterable file rail.
    • Full review writing: inline and file comments, suggestions, thread replies and resolution, and approve / request-changes / comment.
    • Connects straight to GitHub from your machine: no server sees your code.