Product Printerの新機能

Your account, My projects, My feedback, New project and the training course now open inside the same menu and layout as every other page.

The Feedback box now has the same dictation microphone as the chat, wherever speech-to-text is set up for your workspace.

A new instance now looks like Product Printer: black and white, with colour only where something needs your attention, in light or dark mode as your device is set.

Your own colours, fonts and logo from Settings → Branding still replace it.

Every page inside a project now has the same layout as the rest of the app: lists use the full width, forms one readable width, always left-aligned.

The change request pages no longer draw their own top bar, and the rework bench uses the full height of the page.

New project agents run a tested, pinned OpenClaw release instead of whatever "latest" is that day.セルフホスト

The default is ghcr.io/openclaw/openclaw:2026.10.5 pinned by digest. To run another release, set the edge secret OPENCLAW_DOCKER_IMAGE (tag@digest), and run the setup check before relying on it.

After paying or managing a subscription in Stripe you now land back on the project's Billing page instead of a "page not found".

On your first day and after you set up your first project, Product Printer asks "How is it going?" so you can tell the team in one line what is broken or missing.

Your answer is sent as feedback to Product Printer: you can follow it under My feedback, like anything you send from the menu. "Not now" puts the question away; the menu entry "Feedback to Product Printer" stays available at all times.

Training now has its own place in the sidebar, next to Projects: the AI for SMEs course, with your progress kept per person.

Admins find three self-service courses under Admin → Training (AI for SMEs, how the platform works, Selling AI to SMEs). What a team writes about its own process during the course stays in the project, under Training notes; old project training links open the course.

You can now send Product Printer a problem, a change you need or an idea about this app, and follow their answer under My feedback.

Open it from your account menu ("Feedback to Product Printer"), or ask the assistant in the chat: it fills the form and you confirm before anything is sent. You can attach a screenshot and, if you agree, a few technical details (page, version, browser, recent errors) — never client data.

Plainer words for advisors: the Requirements page, the build pipeline and error messages now say what to do, and "AI isn't switched on yet" comes with a button to switch it on.

Admin → PP Orchestrators now leads with "Your PP Orchestrator — hosted by Product Printer (included)"; running it on your own computer or server is under "More options". Approving a change request before the app is set up now links to the Admin dashboard.

On a phone, a project page now has one menu and room for the project name; the Account page shows Telegram and Billing only when your workspace has them.

The project menu has a "Workspace menu" entry for everything else. On a change request, the decision form gets the full width, and the price field shows an example ("e.g. 1250") instead of a price.

Setting up two-factor sign-in works again after a cancelled or reloaded attempt, and the invitation page picks up where you left off.

"You're now logged in" now appears only after the 6-digit code, and after a reload the invitation page goes straight to the authenticator step instead of asking for the password again.

Your language is now a setting of your account: choose it once in Account settings and it follows you on every device you sign in on.

The language switcher is gone from the menus once you are signed in. E-mails we send you use the same language where they are available in it, and notifications now also reach you on Telegram when you have linked it.

Every pull request of a client app now gets an automatic design check: overlapping buttons, sideways scroll and broken images block the merge.

The check opens the app at phone, tablet and desktop widths and comments a table with screenshots on the pull request; the playground shows "Design check: N issues" with a link. Clipped text, small tap targets, contrast, missing alt text and console errors are warnings. Known exceptions go in `.avodev/design-check.json`, each with a reason.

A change pushed straight to an app's main branch, without the merge gate, is no longer deployed: the project shows "Unreviewed change on main" with Revert and Review.

Revert opens a pull request that undoes it; Review creates a change request, and approving it lets deploys resume. Existing apps get this with their next template update.

When your agency prices a change request, you accept the price on the request before it is built, and each promised result is checked by a test.

The workstep waits until you click Accept price; declining cancels the request. Projects without a client of record keep booking the price at approval.

Who is responsible now decides who merges and who pays: clients can ask for help or a review, and each project shows its AI usage and request costs under Billing.

Agencies set the AI margin, support analysis fee, warranty and "Client deploys themselves" under Admin → Billing (per project in Settings). In the playground, "Ask agency to review" makes a priced change request; "Get help" opens a support request: an analysis fee you confirm, then a fix quote. Existing projects: a Champion merges only once "Client deploys themselves" is on. Clients see billed amounts only; AI cost and margin stay with the agency.

AI usage on a subscription or an unpriced model is now billed at its list-price equivalent, the client's own AI is never billed, and a review's price is booked only when the client accepts it.

Admins keep the list prices under Admin → Billing (each change is a new version) and mark a client's own AI under Connect your AI, on a PP Orchestrator that serves only that project. Clients accept a price with one click on the change request.

The playground now turns each wish into a requirement you confirm, then builds it with one test per acceptance criterion, ships it as a pull request and merges it when CI proves it.

Merging deploys, so only an admin, a project owner or maintainer, or the project's Champion can merge. The Merge button stays off until CI is green on the latest commit, every acceptance criterion has a passing test, and every commit names its requirement. A change to an existing requirement goes to your agency as a change request first, and you see their price before it can be merged.

Refining an epic step and the legacy GitHub orchestrator deploy now answer a bad or signed-out request with a clear error instead of crashing.セルフホスト

Before, both failed with "Function exited due to an error" on every call when an optional setting was missing.

Change requests now show their pull request, say in plain words when a build is on hold, and send status e-mails.

The agency's admins get an e-mail for each new request; the person who filed it hears when it is approved, in progress, on hold, merged and live. E-mails go out through the instance's own sender.

Every new project now belongs to an organisation: pick one, or create it on the spot, when you create the project.

Admins can open an organisation to see its projects and start a new one there, mark one organisation as "our company" (the default for new projects), and filter or group the project list by organisation — projects without one get an "Assign organisation" link.

The welcome steps for new users now show your instance's name instead of an old "avodev" label.

Change requests now have the same name everywhere in the app, in every language.

In German the menu entry reads "Änderungsanfragen" instead of the ambiguous "Anfragen". The Organizations and Projects pages now open with one line explaining what they hold.

Contributors on a project now see the "New request" button, and admins can invite people from a project's Members page.

Before, only owners and maintainers saw "New request", although contributors were allowed to submit change requests. Admins who were not members of a project could not invite its team.

An instance deploy now fails when its GitHub environment has no Cloudflare credentials, instead of reporting success without uploading the frontend.セルフホスト

Before, the run warned, skipped the Pages upload and finished green, so the console recorded the new release while the old frontend stayed live. If you deploy the frontend yourself, dispatch with `deploy_pages=false`.

The manual-rework image (browser VS Code on a project's server) is now ghcr.io/product-printer/pp-rework: scanned, signed and 33% smaller.セルフホスト

Every build is checked for known vulnerabilities before it is published, signed with a keyless cosign signature, and ships its SBOM and build provenance. It contains no credential and needs none to build.

A proven requirement no longer turns red when a test run's results can't be found. That run now records nothing, and its CI check shows why.

A workstep whose build failed can now be run again with "Execute step" (or Retry in the pipeline), and a refused run says why.

A retry continues on the same branch and pull request. Steps that were queued behind a run that never started go back to pending, showing the reason.

Traceability now says why a test result doesn't count as proof, for example because the check was cancelled or the change was merged outside the gate.

A workstep's page now also follows a running step: it shows the step's progress and its pull request as soon as it opens, without reloading.

Answers you type into a proposed solution design's decisions are no longer lost when you reload the page.

They are kept in this browser until you commit the design.

Signed-in pages no longer log React hydration errors on load, and they render once instead of twice.

Requirements extracted with "Refine with agent" are no longer lost when you close the drawer or reload the page.

They stay until you add them or click Discard. They are kept in this browser only.

The assistant can now write a requirement for you: it opens the New requirement form and fills it in, and the chat stays usable while the form is open.

Check the filled fields and click Save yourself.

Traceability now counts a test result as proof only when the app's CI check completed successfully, never from a check that was cancelled or failed.

A change request now moves on by itself — in progress, merged, released in a version, deployed — so the client sees where their change is.

"Propose a design" no longer fails with "direction \"internal\" must be inbound, outbound or bidirectional" on small projects.

"New workstep" creates the workstep again instead of failing when it is added at the end.

Your app now has versions: see each release (v1.0, v1.1 …) and what changed in it under Releases.

A platform admin releases a new version from the same page: the version and the notes are proposed from the merged worksteps and change requests since the last release, and can be edited before publishing. It tags the app's repository and creates a GitHub Release.

A requirement now shows the pull request that delivered it, and the version it was released in, as soon as its workstep's PR is merged.

Traceability counted only PRs whose description named the requirement, so PRs built by the agents stayed at 0.

Traceability now shows, for every acceptance criterion, whether its automated test passed, with a link to the test run — and your client can see it too.

Apps created from now on report their test results after every run on the main branch. A developer maps each test to its criterion in `.avodev/requirement-tests.json`; criteria without a test show "No test yet".

New apps start with a green test check: test coverage can no longer drop below the level the app already has, and that level only goes up as tests are added.

After your first week, Product Printer asks one quick question: how likely you are to keep using it, and what's missing.

It appears once per person, bottom right. "Not now" hides it for three days; your answer goes to the Product Printer team without your name.

Acceptance criteria now show up in Traceability and work planning for every requirement, including those added from an extraction or edited by hand.

Requirements created before this update are fixed automatically.

Your instance's public pages now show only its own name, sign-in and legal links, with no marketing text from another company.

This covers the header, the footer, the page-not-found screen and the page titles search engines see.

Generated worksteps give each feature requirement to one step, and any conflict is shown right away instead of after the first change in chat.

Submitting a change request from a project works again instead of failing with a permission error.

Generated worksteps can be committed again when two requirements share acceptance-criterion numbers (AC-01, AC-02…).

Every app you create now checks each change for leaked secrets, vulnerable packages and unprotected data before it can merge.

The checks run on every pull request of the app's repository and fail it on a high-severity finding: a committed secret, a package with a known high-severity vulnerability, a database table without access rules, or a backend function anyone can call without signing in.

Creating a project from "New project" works again instead of failing with "permission denied".

You can accept, reject or defer a proposed requirement from its detail panel, which unblocks the solution design and worksteps.

Your instance no longer needs any AI provider key: models, embeddings and website imports use the keys on your orchestrator.セルフホスト

Only voice still uses a key on the instance, and you can switch it off in Admin → AI models.

Change requests filed as GitHub issues are imported again when your orchestrator runs without the instance's master database key.セルフホスト

The instance checks every imported request against its project's registered repository before saving it.

Your orchestrator now runs build steps and UI designs without your instance's master database key.セルフホスト

The instance gives each job what it needs and records the results itself; design files are uploaded through the instance for that job only, while it runs.

You can now talk with the assistant in the side panel, and it can fill in forms on the page for you to review.

Start voice mode from the side panel to speak and hear the replies. When the assistant fills a field, the field is marked and you can undo it. Take over whenever you want. Nothing is submitted until you click.

New workflow `instance-export.yml`: a full export of your instance (database dump, file listing, restore notes) as a download from the run page.セルフホスト

It uses the same GitHub environment as `build-and-deploy-instance.yml` and only reads your instance.

Members of a managed-cloud instance can now find it from product-printer.ai: they enter their e-mail address and receive a message listing the instances they belong to.セルフホスト

The new ops-directory function only answers a caller holding the dedicated INSTANCE_OPS_READ_SECRET. It returns the instance name, its address and one keyed hash per confirmed member (HMAC-SHA256 with a key derived from that secret), never an e-mail address. The link in that message opens the sign-in page with the address already filled in (`/login?email=…`).

Instances can now report a usage summary (member count, AI spend this month, last activity, release) to the Product Printer operator console.セルフホスト

The new ops-usage function only answers a caller holding the dedicated INSTANCE_OPS_READ_SECRET; it returns counts and totals, never user data. The deploy workflow now also records the deployed release in INSTANCE_RELEASE.

New change requests are drafted with the assistant in the side panel instead of a separate chat on the page.

Click "Draft with the assistant": the side panel opens on this change request with a starter message. The assistant fills the form, you check it and submit.

Everyone on a project can now open its Members page and see who is on the team, and My Projects is one click away from the header and your account page.

Inviting, changing roles and removing people stays with project owners and maintainers.

The repository now builds only the instance itself; the marketing sites are separate projects.セルフホスト

A plain `npm run build` produces the instance with its security headers in `dist/`, whatever variables are set. Old marketing paths (/pricing, /blog, …) redirect to `VITE_INSTANCE_MARKETING_URL` when it is set.

Choose how your instance sends email, and every email carries your brand.セルフホスト

Settings → Email offers your own Resend account or your own SMTP server (cloud adds a zero-setup Standard option). It checks the key, the sender's domain and the SMTP login live, lists DNS records Resend still needs and shows the provider's own error text. "Send test email to me" confirms delivery. Keys and passwords stay in your instance's Vault. Sign-up, password-reset, magic-link and invite emails carry your instance's brand, and every deploy keeps the 13 authentication templates in sync without overwriting the email provider you chose.

A new instance now looks like Product Printer until you brand it, and you can set its colours, corner radius, fonts and favicon in the instance config.セルフホスト

The same colours and font carry into the sign-in and notification emails. Button text on your primary colour switches between white and dark automatically so it stays readable.

When a deployment ships your change request, it now moves to Deployed and you get the "your change is live" email.

A missing field made the deployment step skip change requests silently. Prices are not affected.

The invitation email now takes you straight to choosing your password, then into the instance, instead of the sign-up form.

If the link has expired or was already used, the page says so and can email you a new one. Inviting someone who was already added to a project no longer fails.

Your answers to open questions now turn into proposed changes to your requirements, which you review and accept before anything changes.

The chat now lives in one panel at the side of every project page, with voice dictation, and remembers the conversation.

It replaces the separate chat windows that used to open on some pages.

A new Documents menu keeps the files of a project in one place, and the assistant now uses them when it answers.

The Product Printer website has a new front page that shows, step by step, how an order turns into a running app.

A new solution design step sits between your requirements and the work plan, so you can review how the app will be built before work starts.

A new "What's new" entry in your account menu shows what changed in each update, with a dot on your avatar when there is something you haven't seen yet.

A new sign-in page lets you find your workspace by its address and sign in there.

An instance can show its own announcement banner at the top of the app, set with `VITE_INSTANCE_BANNER` in the instance env; it is off by default.セルフホスト

The beta banner at the top of the app is gone.

The Product Printer blog has been retired: it is no longer linked from the website's menus.

After you sign in, you land where you work: straight in your project if you have one, otherwise on your project list.

Links you open while signed out still take you to the right page once you have signed in.

Long analyses now run in the background and show their progress, so you can keep working and never lose the result to a timeout.

If you have set up two-factor authentication, it is now asked for before any page of the app opens, not only on some of them.