Design — Troubleshooting

“Sign in” shows even though I’m logged into the suite

Your session is valid but Design isn’t recognizing it. The usual cause is that the GitHub connection or product entitlement isn’t in place. Confirm you’ve authorized GitHub in Connect and that Design appears in your launcher. Reloading the page re-runs the silent sign-on handshake.

The sandbox boots but the preview is blank

A sandbox runs whatever your repo’s dev script starts. A freshly created (empty) project has no app to serve until the agent writes one — ask the agent to scaffold something, or import a repo that already has a working dev server. If you imported a repo, make sure it exposes a dev script that binds the port on 0.0.0.0.

Sandbox is stuck in booting or goes to failed

booting means dependencies are installing and the dev server is starting — large dependency trees take a moment. If it lands on failed, the last_error on the sandbox status explains the step that failed (most often a missing or non-zero dev script, or a failed install). Fix the repo’s dev command and re-boot.

The agent’s change made things worse

Don’t try to talk it back out — restore. Every successful turn is a commit, so the History tab lists the states your app has actually been in; pick the one before the bad turn and restore to it. That’s a deterministic undo, where a follow-up prompt is a guess. Since the same commits are in your repository, git works just as well from outside Design.

My build feed is empty on another computer

It shouldn’t be. History lives on the server, not in your browser, so opening the project anywhere shows the same turns — the most recent load first and older ones as you scroll up. An empty feed on a project that has turns usually means you’re in a different workspace, since projects belong to the workspace they were created in.

The agent edited files but I don’t see a commit

Commits only happen on a successful turn, and they go to a destesi-design working branch — not your default branch. Check that branch in your GitHub repo, then open a pull request to merge. If the turn ended in failed, no commit is made and the working tree changes are discarded so your repo never lands in a half-edited state.

Push was rejected

Design never force-pushes your repo. If the working branch has diverged, resolve it in GitHub (or delete the destesi-design branch to let Design recreate it) and retry. Make sure your Connect GitHub authorization is still active — an expired token blocks the push.

Note

The build sandbox never holds your GitHub token. Cloning in and committing out both happen host-side, so a credential problem surfaces as a clone or push error in Design — never as code running with your token inside the sandbox.