June 8th, 2026
New
Improved
Fixed

The headline for this stretch is a public API — teams and power users can now build on top of Chief directly. Alongside that, a round of fixes cleaned up some rough edges that had been trailing for a while.
Public API with personal access tokens
Copy button on raw text and markdown assets
Download any file from its context menu
Markdown spacing now matches Notion
Navigation tabs reordered and retitled
Labels and actions lists now paginate
Pasted-content pills survive copying across chats
Keywords in pasted prompts stay as text, not pills
Deleting a chat while a response is streaming now works
Raw JSON no longer appears in the Chief interface
Actions no longer fail when an item isn't found
Files move correctly while processing is in progress
Upload modal stays open on outside clicks

Chief now exposes a public API. Generate a personal access token in your settings and start connecting Chief to your existing tools, automations, or custom integrations.
Personal access tokens. Create and manage tokens tied to your account for secure, scoped access.
Full OpenAPI documentation. The API ships documented and versioned.

Output formatting follows Notion's spacing conventions. Content you copy from Chief lands cleanly in Notion without manual whitespace cleanup.
Long lists of labels and actions were getting cut off. Both now paginate so every item is reachable.
A one-click copy button now appears on raw text and markdown asset views.
Every file in your workspace has a Download option in its right-click context menu.
Pills added from pasted prompts were being dropped when a chat was copied to another context. They now transfer correctly.
Text pasted into a prompt was being automatically converted into keyword pills. Content you paste now stays exactly as written.
Attempting to delete a thread while Chief was still generating a response would silently fail. Deletion now works at any point.
Tool call output was occasionally surfacing as raw JSON instead of being processed. It's now handled cleanly.
Chief was returning an error when attempting to look up an action that no longer exists. It now handles that case gracefully and continues.
Assets being relocated while still processing could end up in an inconsistent state. File movement now completes cleanly regardless of processing status.
Clicking outside the upload modal was dismissing it before the upload completed. The modal now requires an explicit close action.