v0.5.0

Install or update from inside Claude Code:

/plugin marketplace add madjagstudios/plugins
/plugin install podium@madjagstudios

What's new in 0.5.0

• Writers and reviewers see the ticket's own text, not just its key, so agents that can't open your tracker still know what to build. A draft warns when a ticket only points at the tracker.
• A writer step that changes nothing isn't counted as done: the ticket stops, unless the writer says why no change was needed.
• A per-repo task test runs on your machine after each writer step, outside the agent's sandbox, and its result decides whether the task goes to review.
• A test or full check that fails runs again on the ticket's starting code. Failures that were already there go to review marked as such, and you can accept a task's test results with your reason.
• Reviewers work in the ticket's own copy with a writable temp folder, so they can run the tests, and you can hand them evidence such as a CI run that passed.
• Sync with base brings a fix that landed after a ticket started into its copy. Podium never drops commits it didn't make; it asks whether to keep them.
• Notes for a ticket: your decisions and instructions reach every later planner, writer and reviewer on it.
• Plans go in the folder you choose for each repo, and a plan saved elsewhere is picked up instead of stopping the ticket.
• A sprint's plan stays in Podium's record but out of the PR, unless the repo keeps plans.
• PR descriptions and commit messages are written from the plan's summary, never pasted from the ticket. In a public repo, lines naming another project's ticket, an agent or a term you've marked private are left out, and Podium tells you what it removed.
• A plan can leave checks to the PR's CI. Podium follows that CI, tells you once whether it passed, and auto-merge waits for it.
• A plan that would deploy, publish or delete names those commands, and runs only after you agree to them.
• A file held open by a program no longer dead-ends a ticket: it stops with its work kept and says how to release the file. .NET builds no longer leave compiler servers running.
• Notices: old ones no longer flood a chat that didn't ask for them, several arriving together are each marked delivered, and chats in a worktree see their repo's jobs.
• A stop that the system refuses no longer leaves test or check processes running.
• A draft warns when the repo's CI runs checks its full check doesn't.
• Podium's copies live in a folder without spaces, so tests that build file paths from their own location keep working.

v0.4.0

First public release of Podium, a Claude Code mod that hands work to Codex, Gemini, Muse and other agent CLIs and tracks it in one pane.

Install from inside Claude Code:

/plugin marketplace add madjagstudios/plugins
/plugin install podium@madjagstudios

What's in 0.4.0

• A new sprint opens as a draft on a board in the pane. There you can change who writes and reviews each task, the order of the tickets, Merge when green and how many tickets run at once, and then press Start or ask Claude to start it.
• Open a ticket from the sprint board to see its tasks and why it stopped. From there you can retry it, give it to another agent, inspect its steps and diff, or stop it. Pause and resume a sprint from its card.
• A sprint Podium can't read shows as a card saying so, instead of disappearing.
• A sprint ticket needs no plan: its writer plans it first, Claude sums the plan up, and the board shows its tasks with Approve and Ask for changes. A plan with no tasks can run as one task.
• A ticket can wait for others in its sprint: it starts once they are merged, from the code as merged on GitHub, and says what it waits for.
• A clearer pane. Every screen leads with one line saying where things stand and one main button, and the detail sits in folds. Rows and screen heads are coloured by state again.
• Finished sprints stay listed: yours under Done, other chats' under Other chats. A sprint started in another chat says so.
• Per-repo settings: the commands Claude may run in its copy (for example dotnet), a full check to run before each PR, whether a ticket's PR is squashed to one commit, and the merge method. Sprint drafts can propose commands and a full check; Start saves those settings.
• Writers end with the result of their tests, and a ticket whose tests didn't pass stops before review. Reviewers see the writer's report.
• A sprint's PR is one clean KEY: title commit, its description is the ticket's text and what changed, and it merges the way the repo merges.
• Each notice arrives once, in the chat that started the work. A sprint's news goes to its own chat, and Take them here moves it to another one if that chat is gone.
• The board says how many tickets are running and which are waiting for a free slot.