Work / Case studyWinner · Best Use of Prune API · SharkByte 2026

Nexus

The nexus of development.

Code, Slack and agents in one editor. A thread becomes a task, a gated agent works it on its own branch, and the commit orbits the globe.

Event
SharkByte 2026
Result
Winner · Best Use of Prune API
(01) The problem

Every hop loses context.

Developers bounce between VS Code, Slack and an AI agent all day. A bug gets reported in a Slack thread, someone copies it into an agent, the agent edits code in the editor, and someone pastes the result back into Slack. Every hop loses context, and nobody on the team can see what the agent is actually doing until a PR appears.

Nexus puts the Slack thread, the code it is about and the agent working on it on one screen, linked to each other. Agents run behind a gate, each on its own git worktree and branch. Running an unlisted command, committing or writing outside the worktree needs a human’s approval, and agents never push or merge. A person approves every risky step from the editor, from Slack, or from their phone.

(02) The win

Best Use of Prune API.

Nexus won Best Use of Prune API at SharkByte 2026. An Optimize with Prune toggle routes text-only model calls through Prune and records a signed receipt for every call.