Devlog 2026-11-04: guards for your secrets, uploads in the conversation, background GitHub push

Wave 2 is live: Kaisen sites and builds now protect your own .env files and keys, uploads live in the conversation, GitHub push runs in the background, and the apps page and admin projects got cleaner.

Share

Live as of 2026-11-04, with the guards active. Coverage measured 96% (floor 93%). The first CI run failed because of a test-only logging bug, which held the release until it was fixed; production was not affected.

This is wave 2 of Chas's feedback. Here is what we changed.

Guards so you can't expose your own secrets

Someone was scanning a Kaisen app for .env files. That made us add guards.

  • Kaisen sites return 404 for dotfiles, keys, databases, backups, logs and server source.
  • Kaisen can't write .env files or credential-looking content. It is told to use Build secrets.
  • Uploaded text files and SVGs that contain a credential are refused. The message names the line and the kind, never the value.
  • Bundles and GitHub pushes skip those files.

The path guards in the Kaisen site runtime needed the runtime image to be re-pinned, which we did the same day, so they are now active.

One honest limit: Python and Node apps run their own web server, so the runtime path guard doesn't cover them. They rely on Kaisen's rule to serve one static folder, and on bundles never containing .env or key files.

A security review found two mediums in the new guards, both fixed. Normal config.js pages were wrongly blocked. The scanner also missed SECRET_KEY-style names, URLs with embedded passwords and DigitalOcean tokens.

Uploads in the conversation

File uploads are still a preview. An admin turns them on per project. They are not generally available.

  • Attach with the paperclip, drag and drop, or paste. Do it while writing the brief, asking for a change, or answering a question.
  • Files show on the message they came with.
  • The build page is now one Conversation timeline.
  • A small Files panel lets you manage them.
  • If an upload fails, your draft is kept and you can retry.

Upload errors now give the limit and your number. For example: "That image is 10.2 megapixels (3200 × 3200). The most allowed is 8 megapixels".

GitHub push in the background

Push now runs as a background job. Status shows beside the button, with plain reasons on failure. We also fixed "Push now" being disabled after opening a saved GitHub output.

Why: the 502 on big pushes was most likely this. Push ran inside the request, one GitHub call per file, so a big build could outlast the proxy's limit. That is a diagnosis from the code; we never confirmed it in production logs, so we can't say for certain it was the cause.

We tested pushes on production on 2026-11-04. With a key that lacks the needed permissions, the push reports the failure. With a key that has them, it pushes successfully.

Build page follow-ups

Two more changes went live on 2026-11-04, after user feedback.

  • The Conversation timeline now scrolls in a fixed-height panel and opens at the newest message, with the change box below it. A long build no longer grows the page.
  • Deployment output no longer appears as a long alert. The Live app card has a Last deployment block with a status badge, time and HTTP code, plus a scrollable output window. It is collapsed by default and opens by itself when a deploy failed or isn't healthy.

Apps page and admin

  • The Apps page has one + button. It opens a chooser: image, template or Kaisen.
  • The new-app and new-build pages no longer have a project selector. It is the project you're in, so you can't deploy to the wrong one.
  • Admin > Projects: search as you type, paging, personal projects included, a Features dropdown with checkboxes (Web search, File uploads), and a narrower app limit box.

We also did a browser UX review at desktop and phone width.