Skip to main content
This tutorial takes one small change through Podium’s complete stable loop. You will create an issue, start an agent, inspect its evidence, and close the issue.

Before you start

You need a configured Podium instance, a registered Git repository, and one installed and authenticated harness. Finish installation and setup before continuing. Run these checks from the repository you want the agent to change:
The status output should show a running server and daemon. The machine output should show the repository and at least one logged-in harness.
1

Create bounded work

Give the issue one result that you can verify. This example asks for a documentation-only change:
Copy the issue reference from the output. The examples below use your_issue_ref as that value.
2

Start an agent

Start the issue with an installed harness:
Podium claims the issue, creates its branch and worktree, and starts the agent there. Open the issue in the web app to follow the session.
Podium web inside a decorative macOS-style frame, showing an issue in the Backlog column of the issue board.

The Podium web issue board inside a decorative macOS-style frame.

3

Follow the result

Read the issue and session state without scraping the full transcript:
If the agent asks a question, answer in the session panel. A browser disconnect does not stop the underlying terminal process.
4

Review the evidence

Inspect the changed files, diff, checks, and issue artifacts. An artifact is a server-side copy, so it remains available after the source worktree changes.Do not accept work because the session is hibernated. Confirm the requested change exists and the relevant check passed. See review agent work for the full review path.
5

Finish the issue

If you accept the result without using Podium’s merge action, close the issue:
A successful podium issue action your_issue_ref merge closes the issue automatically. A failed merge leaves it open.The issue should now appear in the done stage with its session and review history intact.
podium issue start creates an isolated worktree for issue-backed work. A direct session can use the repository’s current checkout instead, so choose the issue path when concurrent work could overlap.

Continue from here

Use the same issue loop as you add more agents and machines:
Last modified on September 16, 2026