Repository navigation
PocketContext Crew 0.18.0
Crew 0.18.0
Project coder agents: one agent per code repository, started by you in a terminal
session (Codex, Claude Code), with a copyable session prompt and leased claims so two
sessions never work the same ticket. 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.
How an agent is started
- Every agent has a kind: Webhook (bot), I start it myself (no webhook) or
Person. Existing agents become bots, so nothing changes for Grok bots. - Create one manually started agent per project and name it after the repository, for
examplepocketcontext-crew. Tickets assigned to it and set Ready form its queue, and
the board's agent filter becomes a project filter. - Only bots are ever woken, mapped, or chosen as dispatcher or triage. Webhook setup and
its warnings list only bots, so a project agent never shows a missing mapping. - Cards say "Started manually · no webhook" or "Person"; the agent filter marks them.
Starting a session
- A manually started agent's card has Start a session. It copies a two-line prompt
to paste into a new Codex or Claude Code session; the session then reads its full
instructions from Crew (crew_read {collection: "session", agent}): Crew's template
followed by the agent's brief, so every session gets the current version. - The instructions have the session name itself once (from
$CREW_SESSION, or the tool,
Zellij pane and session id) and report it on every write, list its Ready To do
tickets, claim one only when you pick it, plan and wait for your approval in the
session, release per the repository's AGENTS.md, then comment "Released in …" and set
Done. Reported names are attribution, not identity.
Claims
- The assigned agent can claim its own Ready To do task (
task.claim): it moves to In
progress with a 2-hour lease under the session's name. A second claim gets HTTP 409
already_claimedwith the holder and lease end. task.claim_renewand the claimer's own updates, comments and file changes extend the
lease.task.release(the claimer, you, or anyone after expiry) returns the task to To
do, optionally On hold with a reason. Done ends the claim.- Cards show "Claimed by …" with the lease end on hover, or an amber "Claim expired".
You can Release claim from the task; a live claim asks first. - Task responses carry
claimed_by,claim_untilandclaim_state(liveor
expired), also a read filter. Claims never send webhooks; the Grok-bot execution
protocol is unchanged.
Also
- The Guide explains project agents and coding sessions.
- A comma that arrives without a key press (autocorrect, mobile keyboards) finishes a
label chip.
Upgrade
Follow Crew 0.17.0 to 0.18.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.18.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.18.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.18.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.