Runs

A run is a single agent execution within a workspace. When you type a goal and press Enter, Jinzo creates a run, launches the agent, and tracks everything that happens — tool calls, file changes, token usage, and costs.

​

Run Lifecycle

Each run progresses through a series of statuses:

​

Turns

A run is composed of one or more turns. Each turn represents a single interaction cycle — the agent receives input, reasons about it, calls tools, and produces output. Jinzo tracks per-turn metrics:

​

Tool Calls

Every tool the agent invokes during a run is logged. Jinzo records:

• Tool name and arguments
• Execution result
• Duration and status (success/failure)
• Nested tool calls (e.g., subagent tools)

Tool calls are visible in the workspace events timeline, giving you full visibility into what the agent did and why.

​

Tool Approval

Some tools require explicit approval before execution. Pre-approved tools run automatically: All other tools trigger an approval dialog in the workspace UI. You can approve, reject, or provide input before the tool executes. Permission behavior is configurable via permission modes.

​

Context

Before starting a run, you can attach context to help the agent understand the task:

​

Artifacts

Runs can produce artifacts — outputs that are stored and accessible after completion:

​

Session Resumption

Runs are tracked with a session ID. You can:

• Continue a previous session to pick up where you left off
• Fork a session to branch off from a specific point
• Resume after the app restarts using the /resume command

Session resumption preserves the full conversation history and context from the original run.

​

Cost Tracking

Jinzo tracks the estimated cost of each run in microdollars (USD * 1,000,000) to avoid floating-point precision issues. Costs are broken down by:

• Model — which LLM was used for each turn
• Turn — per-turn token usage and cost
• Run total — aggregate cost across all turns

View cost data per-run in the workspace sidebar, or see aggregate costs in the stats dashboard.

​

Workspace Diffs

At the start of each run, Jinzo captures the Git HEAD SHA. After the run completes, it computes a unified diff against the base ref. This diff shows exactly what the agent changed and is displayed in the diff viewer. Each diff includes:

• Full unified diff text
• List of changed files
• File stats (additions, deletions, modifications)

​

Sleep Prevention

When enabled in Settings, Jinzo prevents your Mac from sleeping during active runs using macOS power management. Sleep prevention is released automatically when the run completes or the app quits.