Skip to content

PocketContext Crew 0.19.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 10:37
Immutable release. Only release title and notes can be modified.

Crew 0.19.0

Releases and in-session approval: coding sessions approve work with you in the
terminal, and Crew now records that approval and which release shipped each task.
Tasks can also be closed as Won't do. This release has one data migration; back up
before upgrading. No protocol version or managed instruction block changed, so webhook
delivery is not paused. capabilities_digest changes. Run skill once after upgrading
and refresh MCP connector tool schemas.

Releases and in-session approval

  • Tasks have a Release (for example 0.19.0, at most 32 characters), editable in
    the task dialog. Cards with a release show "Shipped in 0.19.0".
  • When you approve a result in a coding session, the session closes the task in one
    update: Done, the release and review_mode: "in_session", with your name as
    approved_by when it knows it (otherwise owner). Crew stamps approved_at itself,
    and the task dialog shows "Approved in session by …, ". Reported names are
    attribution, not identity.
  • in_session is accepted only on a Done task. Moving a task out of Done (by an
    update, a claim or a review request) clears the approval and keeps the release.
  • The session instructions (crew_read {collection: "session", agent}) say so in their
    Close step, and add: if you decide not to do a task, the session comments why and sets
    it Won't do.

Won't do

  • The status select offers Won't do (wont_do). Like Done it ends a claim, never
    wakes a bot, is left out of overdue wakes and is blocked by a pending review; leaving
    it reopens the task.
  • The board keeps four columns. The Done column holds Done and Won't do tasks (Won't do
    cards carry a chip), grouped by release, newest release first and "No release" last.
    It shows tasks changed in the last 7 days; Show older (N) reveals the rest.

Filters

  • The board has a release filter (All releases, each release, No release), kept in the
    address like the agent and hold filters (#/tasks?release=0.19.0).
  • crew_read tasks accept release (exact; "" selects tasks without one) and
    status accepts wont_do. The SQL tasks view gains release, review_mode,
    approved_by and approved_at.

Upgrade

Follow Crew 0.18.x to 0.19.0: take a complete backup, replace the
binary or image, upgrade paired clients, run skill once and refresh MCP connector
tool schemas. An older binary refuses the migrated database; rollback means restoring
the backup.


PocketContext Crew 0.19.0: notes, tasks and human review for AI agents in one binary.

Linux amd64 and arm64: static musl binaries. macOS arm64: macOS 15 or later, ad hoc signed. Windows amd64: statically linked MinGW build, unsigned.

Install on Linux or macOS into the project folder: curl -fsSL https://github.com/pocketcontext-labs/pocketcontext-crew/releases/download/v0.19.0/install.sh | sh -s -- /absolute/project/folder

Install on Windows (PowerShell): $env:CREW_INSTALL_DIR = 'C:\absolute\project\folder'; irm https://github.com/pocketcontext-labs/pocketcontext-crew/releases/download/v0.19.0/install.ps1 | iex

Both installers require the target folder, usually the project folder beside pocketcontext.db (it may be inside iCloud Drive, OneDrive, Dropbox or Google Drive).

See the README.