Changelog

Feature

Batch export for project files

Export multiple project files at once instead of downloading them one by one.

Placeholder body copy: exporting used to mean opening each file, clicking export, waiting, and repeating. For anyone working across a large project that added up fast, especially right before a deadline when every extra click felt like friction.

How it works

Select any number of files from the project list, choose a format, and the export runs as a single background job. You get a notification when the archive is ready instead of staring at a progress bar.

  • Select any number of files from the project list
  • Export as a single .zip archive, or as individual files
  • Large exports run in the background so you can keep working
  • A notification lets you know when the archive is ready to download

What's next

Placeholder body copy: scheduled/recurring exports and direct export to connected cloud storage are being explored for a future release.

Improvement

Faster search across large projects

Search results now return noticeably faster on projects with thousands of items.

Placeholder body copy: as projects grow past a few thousand items, search had started to lag noticeably, sometimes taking a couple of seconds to return results. This release rebuilds how the search index is stored and queried.

What changed

The underlying index now updates incrementally instead of being rebuilt from scratch on every change, and queries run against a more compact in-memory structure.

  • Typical search response time dropped by roughly 70% on large projects
  • Search-as-you-type feels noticeably smoother, even on slower connections
  • Indexing now happens incrementally instead of rebuilding from scratch

Placeholder body copy: smaller projects should feel about the same as before, since the difference is most noticeable once you cross a few thousand indexed items.

Feature

Threaded comments

Replies now nest under the original comment instead of appearing as a flat list.

Placeholder body copy: comments used to appear as one long flat list in the order they were posted, which made it hard to follow a back-and-forth once a discussion had more than a few replies.

Threaded replies

Replying to a comment now nests that reply directly underneath it, so related messages stay grouped together instead of getting mixed in with unrelated ones.

  • Reply directly to any comment to start a thread
  • Collapse a thread to tidy up a busy discussion
  • Jump straight to a thread from a notification

Migrating existing comments

Placeholder body copy: comments posted before this release are shown as a flat list at the top of the thread view, since there was no reply relationship recorded for them originally.

Fix

Fixed a bug where large uploads could silently fail

Uploads over 200MB no longer fail without an error message.

Placeholder body copy: on a slow or unstable connection, uploads over roughly 200MB could fail partway through without showing any error — the progress bar would just stop moving, leaving no clear next step.

Root cause

The uploader wasn't retrying failed chunks, and a single dropped chunk silently stopped the whole upload instead of surfacing an error.

  • Failed chunks are now retried automatically, up to three times
  • A clear error message appears if an upload can't complete
  • You can resume an interrupted upload instead of starting over

Placeholder body copy: thanks to everyone who reported this one with enough detail to reproduce it reliably — that made it much faster to track down.