GyreDownload
ProductPricingChangelogDocsSecurityDownload

Changelog

What has shipped in Gyre, newest first.

Phase 9

Gyre Cloud and self-hosted Gyre Server

Teams share one timeline per change, hosted at api.gyreapp.io or on your own servers.

  • Join Team with an invite code or single sign-on (OIDC with PKCE). A consent dialog says what is shared.
  • Shared timelines: teammates' commits, reviews and pipelines land on your change live.
  • Webhooks for GitHub, GitLab, Render and Sentry replace polling, with signatures verified.
  • Team tokens: an admin shares one code-host token; teammates without one still see reviews and CI.
  • Self-host with Docker Compose or the Helm chart. Postgres over verified TLS, secrets sealed with AES-256-GCM.
  • Pair a phone through the relay, ready for the mobile companion.
Phase 8

Observe, fix, verify

Production errors come back to the line that threw them, and fixes are checked after they ship.

  • Error lens: "142 errors in 1 h, since deploy 14:02" on the exact line, from Sentry or plain platform logs.
  • Stack traces parsed from Node, Python, Go, Java, Kotlin and Rust logs and mapped to the deployed commit.
  • Each error is attributed to the deploy that started or spiked it, traced across repos.
  • AI root cause and fix with your own model, previewed before anything is sent; the fix opens as a review.
  • Verify compares error counts before and after the fix deploys, then resolves or reopens.
Phase 7

Staging, production, gates and rollback

Promote a merged change through your environments without leaving the editor.

  • Deploy to Render, Helm or Argo CD per repo and environment.
  • Staging waits for health, a health URL and smoke tests; logs stream in the Gyre Deploys channel.
  • Production gates: approved reviews for every change shipped, named approvers, UTC deploy windows.
  • Roll Back on every environment, never gated.
  • Change sets deploy in dependency order and roll back in reverse, warning about irreversible migrations.
Phase 6

Review mode and the AI reviewer

Review, approve and merge from one inbox across GitHub and GitLab.

  • Reviewer inbox across every connected host, ready-to-review first.
  • Review mode with native diffs, inline threads and an action bar: Approve, Request changes, Merge.
  • AI reviewer with line-anchored comments, using Anthropic, OpenAI or Claude Code with your own access.
  • Every AI request is previewed with its exact text and destination before it is sent.
  • Release notes from merged requests, grouped by label.
Phase 5

Connectors, CI and merge requests

The first four stages connect to GitHub and GitLab.

  • GitHub (including Enterprise Server) with Actions; GitLab (including self-managed) with GitLab CI.
  • Live pipelines with clean logs; a failed job jumps to its failing line; rerun from the editor.
  • Create merge requests with a description drafted from your commits.
  • pre-commit, Husky and Lefthook failures shown as diagnostics.
  • Adaptive polling that respects rate limits; tokens kept in the OS keychain.
Phase 4.5

Multi-repo workspaces and the MCP server

A workspace spans repos and understands the contracts between them.

  • gyre.workspace.toml lists repos, their roles and their contracts (OpenAPI, SQL migrations).
  • Impact analysis: renaming a column reports the queries, handlers, routes and frontend calls it affects.
  • A local MCP server gives AI agents, including Claude Code, the workspace map, search and contract traces.
  • Change sets: one change across several repos is one timeline entry.
Phase 4

The local engine

gyred, a Rust engine, does the heavy work off the editor's UI thread.

  • Timelines stored in SQLite and kept across restarts.
  • Credentials in macOS Keychain, Windows Credential Manager or Secret Service; never readable over RPC.
  • Local RPC p95 of 0.17 ms; keystroke latency unchanged under 1,000 events per second.
Phase 3

The Gyre workbench

Timeline, Reviews, Deploys and Errors become native views in the editor.

  • Gyre Dark and Gyre Light themes, Inter and JetBrains Mono bundled.
  • The Flow panel, a workspace switcher and a status bar that follows your change.
  • Status is always shown as an icon and a word, never by color alone.
Phase 2

Performance program

Startup and typing budgets checked on every change to the editor.

  • Deferred startup work in the workbench and dropped built-in extensions nobody asked for.
  • Memory 1,176 MB against 1,451 MB for the stock editor on the same machine.
  • A guard that fails the build when a new built-in extension starts eagerly.
Phase 1

Gyre, built on Code - OSS

A rebranded editor with the Open VSX extension registry.

  • Gyre's own name and icons; telemetry off by default; no Microsoft-proprietary extensions.
  • Extensions install from Open VSX.
  • Cold start 1,123 ms against 1,233 ms for the stock editor.