Repository navigation
Description
The redesigned playground (Design V2) is now live behind a feature flag at https://playground.accordproject.org. It replaces the single-screen editor with a guided, step-based flow: Template → Text → Data → Logic → Simulate → Deploy.
It is still work in progress, and we would love the community's help to shake out bugs before it becomes the default. This issue is the hub for that effort.
How to enable Design V2
On the live site
- Open https://playground.accordproject.org
- Click the Settings (gear) icon in the sidebar
- In the General tab, switch on Enable Design v2 (Work in Progress)
- The page switches to the new layout. To switch back, use the gear icon at the bottom of the new left rail and turn the toggle off.
The setting is stored in your browser (localStorage key isDesignV2Enabled), so you can also run localStorage.setItem('isDesignV2Enabled', 'true') in the browser console and reload.
Locally
git clone https://github.com/<you>/template-playground.git
cd template-playground
npm install
npm run devThen enable the flag as above. The V2 code lives in src/components/designV2/, its state in src/store/designV2Store.ts, and unit tests in src/tests/components/designV2/. See DEVELOPERS.md for more.
What to test
Walk through every step with each sample template, then try to break it:
- Introduce errors in
text.md,model.cto,data.jsonandlogic.tsand check the error messages, status chips and checklists - Switch templates mid-flow, use Back/Next and the stepper, reload, and open share links
- Import templates (library and file; URL import is being removed in Design V2: remove "Import from URL" (blocked by CORS for most hosts) #1118) and every Deploy action (PDF, Markdown, share link, clipboard)
- Narrow / mobile viewports, keyboard-only navigation, screen readers, and different browsers
Reporting a bug
- Search open issues first to avoid duplicates
- Open a new issue with Design V2 in the title, steps to reproduce, expected vs actual behaviour, browser/OS and a screenshot
- Mention this issue (
Part of #1096) so it is linked here
Fixing a bug
Comment on the bug issue to say you are working on it, then open a PR that references it (Fixes #<issue>) and includes a test where practical. Please keep each PR to one bug.
Starter bugs
These were found in a quick pass over the live site and are good places to start. Status as of 16 Nov:
- [Design V2] Data step marks "data matches model" as failed for errors in text.md #1097: fixed by Sayan codes dev/1097/text error data step #1105 (merged 16 Nov)
- [Design V2] text.md errors show a minified error name and "line -1 column -1" with no editor marker #1098: fix in fix(design-v2): clean up text.md errors and add editor marker (#1098) #1102, changes requested (must keep the source tag Sayan codes dev/1097/text error data step #1105 routes on)
- [Design V2] Preview shows a stale agreement with the "live" badge when text.md has an error #1099: fix in fix(design-v2): indicate stale preview and disable downloads on error (#1099) #1106, changes requested (revert the CSS reformat only)
- [Design V2] Logic step content overlaps and is clipped at mobile widths #1100: fix in fix(design-v2): stop Logic step overlap and clipping at mobile widths #1104, changes requested (narrow it to the [Design V2] Logic step content overlaps and is clipped at mobile widths #1100 fix)
Thank you for helping make the new playground solid!
Activity
sayanCodesDev commentedon Nov 13, 2026
Hi @mttrbrts,
Following up on the Starter bugs checklist in this tracking issue. Pull requests have been submitted for all four items and are ready for maintainer review:
text.mderrorsEach PR includes relevant test coverage or visual verification. Once reviewed and merged, all starter bugs from the list can be checked off!
mttrbrts commentedon Nov 16, 2026
Bug bash progress update (16 Nov)
Thanks to everyone who has reported bugs, opened fixes and reviewed each other's PRs. All open Design V2 PRs have now been reviewed. Here is where things stand.
Starter bugs
Merged today
Approved, waiting on CI
Changes requested
#1102, #1104, #1106, #1084, #1044, #1073. Each PR has a review with the details. Push an update and we'll take another look.
Also in progress
CI notes for contributors
mainto pick it up.rebuild-sandbox.spec.ts"a formula cannot take over the worker…", is flaky and fails onmaintoo. If it's the only failure on your PR, it's not your change. That's tracked in Flaky E2E: rebuild-sandbox "formula cannot take over the worker" times out behind a modal #1117, which is a good pick for anyone who enjoys Playwright.What's next
The plan is to make Design V2 the default view, with the classic layout still available from Settings and a one-time banner to switch back (#1116). The bugs above should land first, so fixes to the open starter bugs are the most valuable thing right now.
Please keep reporting what you find: put [Design V2] in the title, include steps to reproduce, and add
Part of #1096.mttrbrts commentedon Nov 16, 2026
Quick follow-up: #1064 (stops a double-click starting two AI runs) and #1078 (Format disabled on an empty data editor, closes #1077) have now passed CI and are merged.
That makes six Design V2 fixes merged today: #1105, #1067, #1092, #1083, #1064 and #1078. Thanks to everyone involved!
mttrbrts commentedon Nov 16, 2026
New issues open for contributors, all labelled help wanted:
#data=link should go straight to the shared template on Text.rebuild-sandbox.spec.ts. It fails onmaintoo, so if it's the only failure on your PR, it isn't your change. A good one for anyone who knows Playwright.#1119 and #1120 overlap (both decide which view V2 opens on), so please comment on the issue before starting, to avoid duplicate PRs. Each issue includes the cause, the files involved and acceptance criteria.
mttrbrts commentedon Nov 16, 2026
One more for contributors, labelled help wanted:
org.accordproject.runtime@0.2.0.Request.This overlaps with #1043 (Simulate pre-fills the Counter sample's
CounterRequest), so one PR could fix both. Please comment on #1121 before starting.mttrbrts commentedon Nov 16, 2026
New feature issue for Design V2:
.vscode/extensions.json(recommending the Accord Project extension) and anAGENTS.mdthat points agents to accordproject/skills.This replaces the clipboard-based "Copy for AI" idea from the RFC #1108. A contributor has already offered to take it on in #1108, so please check #1122 before starting anything similar.
mttrbrts commentedon Nov 16, 2026
New PR for Design V2:
Please try it on the PR's Netlify deploy preview, especially as a first-time visitor (clear site data first) and when switching between classic and V2 with edits open, and report anything odd here.
Known gap, not covered by #1123: the V2 Simulate step doesn't yet show the AI execution-mode controls that the classic layout has.
Jenil1905 commentedon Nov 18, 2026
I investigated the concurrency concern raised during the review of #1064 and reproduced it on clean upstream
mainat commit4f760d0, using both sandbox and forced LLM execution with controlled pending responses.After initializing the contract and completing one trigger, I held a subsequent trigger pending and called
initContract()again. The second initialization cleared the chain, execution history, displayed state, and persisted chain before the executor rejected it because another execution was already in progress.The public
initContract()catches the busy error instead of propagating it. Its cleanup also setsexecutingOperationtonullwhile the original execution is still pending.The resulting behavior depends on the original execution:
isContractInitializedremainsfalse, preventing subsequent triggers.I reproduced this with deterministic deferred promises across both execution modes.
This appears separate from #1107, which focuses on restart confirmation. The concurrency guard needs to reject the competing initialization before it mutates execution state.
No repository source or test files were modified during this investigation.
coinjanet5-source commentedon Nov 20, 2026
Hi! I work with supplier and service agreements, engineering procurement, and tender documentation. I’d be happy to help test Design V2 manually from a contracts user’s perspective.
I can walk through a sample template using fictional data, check whether the steps and validation messages are clear, and report any reproducible issues with steps, expected vs. actual behaviour, and browser/OS details.
Is there a particular template or workflow you’d like me to test?