Skip to content

Crew v0.6.0

Choose a tag to compare

View all tags
@alexselig alexselig released this 11 Sep 23:32
v0.6.0
ab58933
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Context that follows the session

  • Native conversation resume is the default; event-log size is no longer mistaken for model context capacity.
  • Brief-backed sessions load their context automatically through Copilot's startup prompt.
  • New sessions offer a model dropdown from the installed Copilot CLI, defaulting to GPT-6 Astra, plus an explicit working directory.
  • Resume preserves later /model selections, and launch retries retain conversation lineage.

More dependable daily operation

  • Autopilot indicators stay synchronized across workspaces, windows, split event writes, and restarts.
  • Atomic roster saves, validated backup recovery, batched restoration, and retryable transcript writes reduce data-loss paths.
  • Output pauses when transcript capture is blocked and resumes after recovery.
  • Workspace shortcuts, transcript composer capture, bounded terminal replay, and preview-navigation boundaries are corrected.
  • Storage and native-opening failures are surfaced rather than silently discarded.

Safer installation and releases

The macOS installer selects the exact architecture, validates the signed/notarized bundle and active native dependencies before quitting, stages replacement on the same volume, and retains the previous app until launch is confirmed. It never deletes session data or bypasses Gatekeeper.

All platforms are staged together and release downloads are checked before publication.

Platform Download
Apple Silicon DMG
Intel Mac DMG
Windows Installer

Both macOS builds are Developer ID signed, notarized, and stapled. Windows builds remain unsigned, so SmartScreen may warn. Portable ZIPs are available below.

Preservation limits: this release does not implement the planned lossless session vault or guarantee 100% recovery after storage failure or power loss. Briefs are summaries; provider history and attachments still need independent backups. Installer launch confirmation checks process presence, and forced termination may require manual recovery of its staging backup. See the README for details.

Assets 13
Loading