Artifacts and results
A task ends with a result you can check. Polo records what it read, what it proposed, what ran and what it verified, and it keeps the files a task produced. This page covers the result view inside a task and the Artifacts page (under Apps → Artifacts).
Review a task’s result
Section titled “Review a task’s result”Open a task from Tasks. The view leads with one sentence on what happened and the next action, then:
| Part | What it tells you |
|---|---|
| Progress strip | The stages the task went through: Received, Investigated, Change proposed, Approved, Applied, Verified, Done. A failed or canceled task stops at the first stage it did not reach, with the reason. |
| Changes | Every change Polo proposed, with its review, who approved it and its outcome. |
| What Polo found | The reported summary and the reports Polo published. Press Read the report to open one. |
| Open points Polo could not confirm | Things the agent could not establish. Read these before acting on the result. |
| Activity | The steps in plain words: what it read, which checks it ran, what it waited for. The newest 24 tool steps are listed; earlier ones are recorded. |
| Polo and its helpers | Which agents worked on the task. A helper works with its own agent’s tools and rules. |
| Technical details | Identifiers, and AI usage by model. |
The summary line counts the changes and how each ended, for example “1 change made and verified”, and how many points Polo could not confirm.
Evidence
Section titled “Evidence”Polo’s claims are tied to what it observed.
- A statement in a report cites the step it rests on. Cited steps open where Polo recorded them in the activity.
- A citation of a knowledge document names the version and the lines.
- A change is checked after it runs with a separate read. The change’s card says what that check was, such as “Polo runs a fresh plan to confirm nothing is left to change” for Terraform, or “Polo reads the message back from the channel” for Slack.
- When Polo could not confirm that a change ran, the outcome reads Outcome unknown. Press Verify outcome before asking for another change to the same thing.
The Artifacts page
Section titled “The Artifacts page”Artifacts lists what Polo’s tasks produced across the workspace. It has two parts.
Workspace outputs
Section titled “Workspace outputs”These are change bundles and private task reports.
- A change bundle is a set of file changes an agent made in its own workspace copy that passed their offline checks. The row shows how many files changed and its lifecycle. Open Review changes and the offline check to read it, or download the bundle to review the complete change manifest.
- A report is a document an agent published for a task. It is private to the workspace.
- Open task takes you to the task that produced an output.
A change bundle does not reach your repository by itself. Publishing it as a draft pull request is a separate change that needs approval, and so is marking the draft ready and merging it.
| Lifecycle | Meaning |
|---|---|
| Passed offline sandbox checks | The changes passed the checks registered for the repository |
| Not accepted by Polo’s review | The supervisor’s review did not accept the result |
| Publication awaits approval | A request to publish it, for example as a draft pull request, waits for a person |
| Approved and published | It was published; the row names what it was published as |
| Publication approved but unconfirmed | Polo could not confirm that the publication happened |
| No publication recorded by Polo | Polo has no record that it was published |
| Merge approved and pending | A merge of Polo’s published head was approved |
An agent can publish a report as a page: a dashboard or report at an address of its own. Publishing again to the same page replaces what it shows with the newest edition.
- Members of the workspace can open a page when signed in.
- An administrator can press Share by link. Anyone who has the link can then open the page without signing in, including what an agent publishes to it later. Stop sharing makes the old link stop working.
- A page is a static document. Scripts, forms, frames and outside resources are refused when it is published.
Let an agent publish reports
Section titled “Let an agent publish reports”- Edit the agent on the Agents page.
- Switch on Publish private task reports.
Publishing a report needs no approval, because it writes only inside Polo. An agent needs this tool before Polo can propose a fix in an incident, since a fix must come with an incident report.
Other results Polo produces
Section titled “Other results Polo produces”- Google Docs and Slides. With a connected Google account, an agent can create or replace a document or presentation after the exact content is approved. They are listed on the Docs & Slides page.
- Draft pull requests. With approved write paths on a repository, an agent can open a draft pull request of a verified change bundle after approval. See Fix a slow pipeline.
- Infrastructure diagrams and Terraform projects. These come from the Infrastructure page, not from a task. See Cloud and infrastructure.
Limits
Section titled “Limits”- An agent can publish at most five reports per run, each up to 6,000 bytes. An HTML report can be up to 40 kB.
- Reports can be granted to tasks started by an uptime monitor, but not to tasks started by a Grafana or Slack alert source.
- Stored reports are checked against their recorded digest when they are read.