Reading the stored record for this page
Reading the stored record for this page
For grant teams whose milestone payment is waiting on a review. UNSTUCK runs a check for each ask you pick on the last commit before the review, and tags it Still missing, Works or Not sure, with the line that decided it. Paste your fix and it reruns the same checks on it.
See a real example from the Canton Dev Fund, issue #887
Your work is delivered, then a reviewer lists what's still open on the commit they looked at. You guess what will satisfy them, push a change and wait for another look.
61 days from delivery to acceptance
This part works today. Paste one link, confirm the asks NEAR AI ticks and give each a check. Every tag describes the last commit before the review.
UNSTUCK reads the thread and finds the last commit before the comment. You confirm it before anything runs.
Every run gets a public page with what ran and what came out, on the commit your reviewer looked at. A fix you check gets its own page too.
The last commit before your reviewer's comment, which you confirm before anything runs. Later pushes don't change it. Checking a fix is a separate run.
The checkout and install go online. Each check runs in a fresh container with no network, so the result depends only on the commit and the check. Whether the check fits the ask is your reviewer's call.
Containers: Node 22, Python 3.12, Rust 1.84 without the wasm32 target, Go 1.23 or Alpine 3.20. The install gets 15 minutes. Each check gets 10, with 2 CPUs and 3 GB, and running out of time counts as Still missing.
A failing check is a job an agent can take: the reviewer's words, the line that failed and a command that has to exit 0.
You hire one on NEAR Agent Market and pay on its own checkout. Its fix runs through the same check, and an ask turns Fixed only when it exits 0.
Live today
Checks and run records, NEAR AI picking asks, checking your fix, and an MCP server for agents.
Built
Sign-in, a spending limit and hiring from live agent listings. You pay on Agent Market's own page. Open the hire screen
Not built yet
UNSTUCK's own market listing, so others can hire it there, and a Claude Code skill.
You've delivered the milestone, a reviewer listed what's still open on public GitHub, and those items are what's left before acceptance.
What it can't do yet, what gets published and what it costs.
The check for ask 1 at 5e17c99, the last commit before the review
$ ls mkdocs.yml docusaurus.config.js docusaurus.config.ts book.toml .vitepress/config.ts docs/.vitepress/config.ts 2>/dev/null | grep . || { echo 'error: no docs site config found (mkdocs, docusaurus, mdbook, vitepress)'; exit 1; }
error: no docs site config found (mkdocs, docusaurus, mdbook, vitepress)
exit 1 with the network off, in 800 ms, on 6 Nov 2026
It only looks for a docs site config in the repo, so it can't see a site hosted somewhere else.
Open the run recordUNSTUCK runs a check for each ask you pick on the last commit before the review, and tags it Still missing, Works or Not sure, with the line that decided it. Paste your fix and it reruns the same checks on it.
See a real example from the Canton Dev Fund, issue #887
23 days to the first review38 days after it
“Live API keys in source/tests. … Please move keys and endpoints to environment variables.”
The first evaluation marked it Changes requested over four issues: an unfinished testing guide, API keys hard-coded in the source, no tests for the action layer and E2E steps nobody could reproduce. The asks were specific. Closing all four took another 38 days and two more reviews.
UNSTUCK reads asks written in the thread, not evaluation files like this one yet.
From the evaluation: the reviewer's own run failed until they added a missing dependency.
eliza-dot-aes $ pnpm run test:coverage
Cannot find module 'ethereum-cryptography/aes.js'
A reviewer describes what's missing in sentences, sometimes in a separate file. There's no check you can run.
They reviewed one commit, and your branch has moved since. Green CI on main doesn't show their specific asks are met.
2 public milestone reviews from Canton Dev Fund and Web3 Foundation Grants, rerun on the commit each reviewer looked at: 2 asks, 2 still missing there.
See every review in the studygithub.com/canton-foundation/canton-dev-fund/issues/887
UNSTUCK suggests checks for docs, tests, builds, lint, README, CI, license, Docker and examples, and offers any command your reviewer wrote. Change any of them. Your reviewer sees each one in full.
Its check: $ ls mkdocs.yml docusaurus.config.js docusaurus.config.ts book.toml .vitepress/config.ts docs/.vitepress/config.ts 2>/dev/null | grep . || { echo 'error: no docs site config found (mkdocs, docusaurus, mdbook, vitepress)'; exit 1; }
1Still missingat 5e17c99
error: no docs site config found (mkdocs, docusaurus, mdbook, vitepress)
exit 1, network off, 800 ms
It only looks for a docs site config in the repo, so it can't see a site hosted somewhere else.
Use the record to agree with your reviewer on what each ask needs before you push, or to show a check already passes on the commit they reviewed.
Check a reviewUse the record to agree with your reviewer on what each ask needs before you push, or to show a check already passes on the commit they reviewed.
Each output is saved with its SHA-256 hash, and every record carries a script that reruns its steps with Docker, so anyone can compare without this site.
Run recordRan 6 Nov 2026
ChainSafe/canton-erc20 at 5e17c99
| Step | Network | Exit | Time | Output |
|---|---|---|---|---|
| checkout | on | 0 | 3.2 s | 21850efbe1 |
| check 1 | off | 1 | 800 ms | 4b0af2189c |
…not hosted on one single unified docs page so one can verify…1Still missing ls mkdocs.yml docusaurus.config.js docusaurus.config.ts book.toml .vitepress/config.ts docs/.vitepress/config.ts 2>/dev/null | grep . || { echo 'error: no docs site config found (mkdocs, docusaurus, mdbook, vitepress)'; exit 1; } | ||||
Failing line: error: no docs site config found (mkdocs, docusaurus, mdbook, vitepress)
check 1exit 1
…not hosted on one single unified docs page so one can verify…1Still missing
Failing line: error: no docs site config found (mkdocs, docusaurus, mdbook, vitepress)
Run recordOpen this run recordRan 6 Nov 2026
ChainSafe/canton-erc20 at 5e17c99
| Step |
|---|
It will get the reviewer's words, the line that failed and your public repo at that commit. It won't get your keys or write access.
The same checks run again on that commit with its change applied, network off. This already works for your own fix.
Once they pass, you'll get a pull request and a reply draft that links each check's run. You read both and post them yourself.
It will get the reviewer's words, the line that failed and your public repo at that commit. It won't get your keys or write access.
The same checks run again on that commit with its change applied, network off. This already works for your own fix.
Once they pass, you'll get a pull request and a reply draft that links each check's run. You read both and post them yourself.
You hire one on NEAR Agent Market and pay on its own checkout. Its fix runs through the same check, and an ask turns Fixed only when it exits 0.
Yes. Paste its pull request, commit link or SHA. UNSTUCK applies it to the reviewed commit, reruns the same checks and marks each ask Fixed or not.
Not yet. Any program that reviews on public GitHub works if the asks are in a comment. Linked evaluation files, common at Web3 Foundation, aren't read yet.
Only where a sentence can become a check. If one asks for nothing you can test, leave it out or let it stay Not sure, and ask your reviewer what they need.
No. Every run is listed under Recorded runs, and your milestone gets its own page, both at permanent links. Nothing runs until you start it.
Read the record, not the tag. A pass means one command exited 0 on one commit. Each command sits beside the words it checks, so a sentence of yours that isn't there had no check.
Reading the comment and rerunning the checks are free. A hire costs the agent's price, paid on Agent Market.
UNSTUCK can't make a funder pay. Your reviewer still decides.
Not affiliated with Web3 Foundation or the Canton Foundation. Milestone and run links are permanent. Built at NEAR HACKATHON 2026.
| Network |
|---|
| Exit |
|---|
| Output |
|---|
| checkout | on | 0 | 21850efbe1 |
| check 1 | off | 1 | 4b0af2189c |
check 1
ls mkdocs.yml docusaurus.config.js docusaurus.config.ts book.toml .vitepress/config.ts docs/.vitepress/config.ts 2>/dev/null | grep . || { echo 'error: no docs site config found (mkdocs, docusaurus, mdbook, vitepress)'; exit 1; }
The last commit before your reviewer's comment, which you confirm before anything runs. Later pushes don't change it. Checking a fix is a separate run.
The checkout and install go online. Each check runs in a fresh container with no network, so the result depends only on the commit and the check. Whether the check fits the ask is your reviewer's call.
Containers: Node 22, Python 3.12, Rust 1.84 without the wasm32 target, Go 1.23 or Alpine 3.20. The install gets 15 minutes. Each check gets 10, with 2 CPUs and 3 GB, and running out of time counts as Still missing.
Each output is saved with its SHA-256 hash, and every record carries a script that reruns its steps with Docker, so anyone can compare without this site.
Get the script to run it yourself
A Major Gap I have seen in evidence is it has missing information for self verification by commitee, most of it has to be from person's own side of verification which we can't verify on our end, there are many markdown docs files yes but 1Ask 1: not hosted on one single unified docs page so one can verify, THIS NEEDS IMMDEATE WORK TO BE DONE for Builders and Commitee.