NEKKO AGENT
Docs
Using Nekko Agent
Following verification and PR progress
Agent chats show verification progress above the footer pull-request panel in the desktop app and Local Web UI.
Verification checklist
The checklist reports n of n passed, followed by each check's state, device, current activity and last update. Expand it to follow individual checks or open an evidence link. You can collapse it to keep more room for the conversation.
| State | What it means |
|---|---|
| Pending | Published but not started |
| Working | The agent reports it is checking this item |
| Passed | The agent explicitly reports inspection passed |
| Failed | The reported inspection found a failure |
| Blocked | Something prevents this check; read the activity detail |
| Unknown | No reliable verification result was reported |
| Stale | No update for at least two minutes; this does not itself mean stuck |
These are agent reports, not an independent guarantee. A screenshot captured or a browser tool finished is not evidence that the pixels were inspected. Ordinary plan steps marked done do not count as verification passes. No checklist published means the agent has not supplied structured checks; you can ask it to publish or update its verification checklist and device/activity details.
Pull-request progress
The PR panel shows finished/total head checks, successful/neutral/skipped, pending and failing checks, and any unknown outcomes. Finished includes failures, so all checks finished does not necessarily mean passing. Check details expands the named checks and their links. CI checks opens GitHub's checks tab.
Review threads shows resolved and unresolved thread counts and opens the PR files tab. These are threads, not individual comments, approvals or review requests. One thread can contain several comments.
Unknown means GitHub data could not be read completely, not that there are zero checks or threads. No checks reported is shown only for a complete empty response. The panel uses existing cached polling while the chat is visible. Its checked time is the local observation time, not GitHub's PR edit time. Failed refreshes can retain older observations, which become stale. Sign in to gh or reconnect GitHub if metadata remains unavailable, and confirm access to the repository.
The initial presentation is shared by desktop and Local Web UI. Native phone progress presentation is not included. Links open in the normal external-link flow and do not approve or merge a PR.