Changelog

What changed in each released version, newest first. A version's heading is dated the day it was tagged. CLAUDE.md covers how a release is cut.

0.5.3 (2026-10-07)

A review block in .bishop/config.json names a message reviewer, a command or an HTTPS endpoint. Startup refuses one that can't run or that the sandboxed agent could change. Nothing calls it yet, so a configured reviewer logs a warning that no message is reviewed (#262).
With agent.sandbox on and no nono profile named, startup warns and points at bishop nono setup (#266).
Commands Bishop runs, like the git status behind bishop upgrade, finish writing their output before Bishop reads it. Before, output could occasionally arrive truncated or empty (#252).
The Sandbox docs page opens by saying Bishop's home must sit outside the agent repo (#268).
The Claude Agent SDK moves to 0.3.292 and the Codex SDK to 0.160.1 (#260, #274).
@modelcontextprotocol/sdk moves to 1.32.1 and proxy-addr to 2.0.8 for security advisories (#261, #275).

The Claude Agent SDK moves to 0.3.289 (#244, #245).
The docs site publishes llms.txt, llms-full.txt, and a markdown copy of every page, so a coding agent can read the docs directly. The Quick Start gives a setup prompt to paste into one (#247).

The agent can read a Slack message someone links to or mentions, along with a few around it, through slack_read_message. It reads only from the conversation the turn is running in, and needs no new Slack scopes (#241).
The operator documentation moves from the README to a docs site built from docs/, for bishop.agentdeployment.co. npm run docs:build builds it (#219).

The agent can change a schedule in place with schedule_update, keeping its id. Whoever changes a schedule becomes its owner, and a new cron or time zone moves the next firing (#215).
The Claude Agent SDK moves to 0.3.287 and the Codex SDK to 0.160.0 (#225, #238).
npm audit reports nothing: audited transitive dependencies are refreshed, and Vitest moves to 5 for development (#221, #239).

agent.sandbox: true runs the Claude or Codex agent, and everything it starts, under nono, so the kernel keeps it out of Bishop's database, config, backups, .env, and files shared in other threads. Startup refuses rather than run the agent unconfined once the sandbox is asked for (#185, #186).
bishop nono setup writes a nono profile that lets a sandboxed agent push with SSH and the gh CLI, and turns the sandbox on with it. --name names the profile, bishop by default (#199).
Teams and Gmail agents are told where a conversation is, who can read it, and whether anyone outside the organization is in it, as Slack agents already were (#202).
After ! verbosity, a Codex agent's next turn is told what the new level shows. Before, Codex kept the guidance its thread started with (#207).
Bishop keeps a transcript of what each turn handed the agent and what the agent said, collected with its thread. The upgrade adds a table for it (#211).
Bishop recognizes the agent's own Slack bot, mailbox, and Teams bot among stored senders. The upgrade adds a column for it (#210).
New schedules get sch_ ids. Existing schedules keep their ids, and both forms work everywhere a schedule is named (#203).
The Claude Agent SDK moves to 0.3.285 and the Codex SDK to 0.159.2 (#204, #206, #212).

The agent gets the same description of every sender on every interface, including whether it is a person or a bot and whether it is inside the organization, and Bishop remembers each sender under one id across threads. Scheduled turns come from Bishop's own principal. The upgrade migrates existing schedule owners (#192).
The agent knows what kind of Slack conversation it is in: a DM, a private channel or a public one, and whether anyone outside the organization can read it. It needs no new Slack scope (#198).
npm run dev:teams runs the built branch against a dev Teams app behind a Tailscale Funnel, the way npm run dev:slack does for Slack. Each dev instance now gets only its own interface's credentials, and its state moves to .dev/<interface> (#200).
The README and design docs say Teams can send files, and name Files.ReadWrite.All as the grant channel files need (#189).

Teams takes the same command messages Slack does, like ! verbosity, ! model, and ! help (#173).
The agent reads what was said earlier in a Teams channel thread or group chat when it is mentioned partway through, as it already does in Slack and Gmail (#177).
! stop stops a running turn in Teams and Slack. It is the only way to stop one in Teams (#179).

Codex agents can commit from linked worktrees under the workspace-write sandbox (#171).

Teams can send files from personal chats and channel threads, using consent cards for chats and SharePoint uploads for channels. Scheduled reports use the same paths (#165).
Claude and Codex SDK dependencies are pinned to exact versions so installs stay reproducible (#168).

The agent can send a file back: an upload in a Slack thread, an attachment on the mail in email. It registers the file with file_share and writes <attachment ref="..." /> where the file should appear. Teams can't carry one yet and refuses the tool with a reason (#142).
! model changes the model and the reasoning effort for one thread, either half on its own, with default returning it to the configured value. The setting lasts the life of the thread, so moving one conversation onto a harder model no longer means editing config and restarting every other conversation with it (#162).
The log line that closes a turn names the model that ran, and so does the line for a turn that errored (#162).
npm run dev:slack runs the built branch against a dev Slack app, so a change can be used in a real thread before it merges. It detaches, keeps its state in a gitignored .dev/, refuses a second instance on the same app, and stops itself after ten minutes of quiet (#162).
The container image no longer builds on pull requests (#160).
CLAUDE.md says how an issue gets filed and what a technical note is worth, and drops what its design docs already say (#156, #159).

Bishop runs on Microsoft Teams: it serves the messaging endpoint from its own process, shows a turn while it runs, carries files people attach in a chat or a channel, and bishop teams setup walks an operator from an agent directory to a working app (#124, #125, #126, #130, #135, #138, #143, #145, #148, #152).
The agent stays out of an email thread it was only copied on (#128).
BISHOP_LOG_LEVEL works in .env (#146).

Releases before 0.3.0 predate this file. git log v0.2.0 is the record.