Repository navigation
PocketContext Crew 0.22.0
Crew 0.22.0
The full lifecycle for shared artifact links: discard drafts, update a live link
from a separate draft, let links expire, archive what you no longer need, and
filter the Shared page. One data migration needs a complete backup before
upgrading. Run skill once and refresh MCP tool schemas. Protocol 3 and the
managed webhook instruction block are unchanged, so delivery doesn't pause for
this upgrade.
Shared page
- Filters: Drafts, Live, Revoked/expired and Archived, with counts. Drafts
and Live show by default, and the choice stays in the address
(#/shared?show=...). - Discard a draft you no longer want. It moves to Archived, where
Restore brings it back. Nothing is permanently deleted. - Update of: <title>. A draft can update another artifact's link. When you
publish it, Crew asks: Replace the existing link's content (same link, the
draft becomes the new frozen snapshot, and the draft itself is archived) or
Publish as a new link. When the original link no longer works, only a new
link is offered. - Set expiry on a live link: never, 7 or 30 days, or a date. From that moment
the link stops working with no manual action. - Revoked or expired links show Publish again with a new link (the old
link never works again) and Archive. A live link must be revoked before it
can be archived. - Live cards show the expiry and when the link was last opened next to the
view count. Replace content is now Update content (same link).
Public page
- Unknown, revoked, expired and archived links all answer the same plain 404,
now worded "This link is no longer available." Nothing outside Crew can tell
them apart.
Agents and data
- Artifacts gain
expires_at,replaces,archived,archived_atand
archived_by, and reads add a derivedstate(draft,published,
expired,revokedorarchived).crew_readartifacts hides archived ones
unlessarchived: true. - Agents may set
replacesonartifact.createandartifact.update, so they
can draft an update of a live link. The newartifact.set_expiry,
artifact.archiveandartifact.restoreare owner-browser-only like publish,
replace and revoke: work clients get HTTP 403.artifact.publishtakes
expires_atand, for an update draft,mode(replaceornew). - Publish and replace events keep the frozen snapshot they published, and replace
also keeps the one it replaced, so every published version stays in history.
Upgrade
Follow Crew 0.21.0 to 0.22.0. Back up the complete stopped
project and private webhook key before replacing the binary or image. Upgrade
paired clients to match. Older binaries refuse the migrated database, and rollback
restores the complete pre-upgrade backup, losing changes made since it.
PocketContext Crew 0.22.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.22.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.22.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.