Artifacts
hob automatically captures the durable outputs of agent work — commits, issues, and plans — each linked to the conversation that produced it.
As agents take on more of the work, the hard part shifts from doing to staying organized: knowing what changed, why, and which conversation produced it. Artifacts are how hob keeps that straight.
When an agent uses hob to do something durable — make a commit, file an issue, produce a plan — hob records it as an artifact and links it back to the exact conversation, and turn, that created it. There's nothing to tag or file by hand; it happens as the work happens.
What becomes an artifact
| Artifact | Created when | What it links to |
|---|---|---|
| Commit | an agent or you run hob git commit | the turn that made it — and opens the commit diff |
| Issue | an issue is created from a conversation (handoff or hob issue) | the Issues panel — carries live, closed, or deleted status |
| Plan | an agent produces a plan in plan mode | the plan turn — carries its state (approved, handed off, or dismissed) |
Agents create commit and issue artifacts by using hob's CLI (hob git commit, hob issue).
They know to do that because Managed hob instructions (Settings → Agent) keeps hob's CLI
guidance in your agent instruction files — it's on by default. If you turn it off, agents
won't produce those artifacts on their own. Plans, and anything you do through the hob UI, are
captured either way.
Where artifacts appear
Artifacts show up in the Activity feed, attached to the session that produced them. Each session lists its artifacts as chips — click one to jump straight to the turn behind it. A commit also opens its diff; an issue deep-links into the Issues panel.
A single piece of work often spans panes — a planning pane, an implementer, a reviewer.
hob git commit --link-pane <pane> links a commit to those other contributing turns too, so
the artifact appears on each of them (the extras show as also linked).
Why it matters
Artifacts turn a stream of agent conversations into an auditable record. For any commit or issue, you can trace back to the conversation that produced it — so the why behind a change never gets lost, even months later.
That traceability is core to hob's goal: keeping professional engineers organized in the agentic era, when far more is happening, far faster, across far more sessions than before.