Anytype Desktop 0.55.0 – Let’s Discuss

In that scenario, it seems like Collections are merely serving as a ‘default page’ for when you don’t want to set up a Page or a dashboard.

If that’s the case, instead of making users choose between Chat, Page, and Collection when creating a new channel, it would feel more natural to categorize them into just ‘Chat’ and ‘Space’ like before. Then, when someone selects ‘Space’, it could prompt them to ask if they want to create a Page. If yes, it creates a new Page for the homepage; if no, it simply sets a default Collection as the homepage.

Agreed. They should provide that. It’s probably just for discoverablitiy for now. They’ll probably hide it in future releases. for now you can use custom css to tweak the look of your anytype :

Simply at the following to your custom.css file and reload anytype Ctrl + R

custom.css

.socialBlockWrap {
    display: none
}

When the option to do automatic text replacements is enabled, text replacement happens even inside code snippet blocks, which makes it impossible to enter things like --css-variable-names correctly.

@henrywu , @dpr , @Bre , etc :

Here’s my take :

  • First class support for collabration.
  • Simpler UX
  • Out of the way if you dont need it

Yes, my code got replaced all the time. It took me a while to realize why my code didn’t work because -- got replaced with .

It’s dangerous, unpredictable, unacceptable behavior for a Knowledge Management app. If a user cannot predict which objects will survive the deletion of a container, they will simply stop using Anytype for anything important.
Software should never make silent, destructive decisions about data based on hidden attributes or the absence of backlinks. This approach treats my data as “disposable”.

To be clear: any situation involving accidental, automatic, or linked deletion must be strictly excluded by design.
I would much rather confirm a deletion multiple times or have to manually “unlock” objects for removal than live in fear of the next patch and its hidden logic. Safety and transparency should always come before “cleaning up” things automatically. The app should serve the user’s deliberate intent, not make assumptions about what data is still valuable.

I mentioned this in the Anytype Community Space. It’s in a much more useful and accessible spot on the side than at the bottom imo

for everyone

passing it on to the designers :writing_hand:

checking!
(it might be a bug, 'cause when I tested it myself, that option was available…)

You’re right, my description is off, sorry about that. It is about the setting ‘Offline Access’ in Local Storage, not something specific to shared spaces.
I’ll fix the entry.

If you select ‘No home’, a channel should open to the last object opened
Or do you mean adding this as a separate setting?

It might be a good idea to simply change the text.
“Last opened item” would avoid the confusion, I think.

Hello guys, thank you for new release :heart_eyes:

I noticed that in the new release filters can only be applied to properties shown as columns. This creates extra steps when I just want to filter by a hidden property (e.g. exclude “archived” items). I’ve written a detailed feature request suggesting an option like “Show all properties” in the filter dialog — please see it here:

Hi! Not a huge fan of the new colour palette either as it is harder to distinguish between them in dark mode but this is a preference ^^.
However, there are a few behaviour bug bears that may just be an update bug…

  1. the link menu when searching jumps around when scrolling, making it difficult to find the object you want to link to.
  2. multi-select properties — I don’t fully understand why there is now a “selected” category when this is clearly visible in the property box, it’s a doubling of action that jumps the menu around when selecting multiple entries and makes it harder to deselect entries when double clicking by accident.
  3. a new block is added when simply jumping down an object using the arrow keys, this also happens when placing the cursor in a blank spot with the mouse.
  4. blocks are fully selected when editing, making them easy to delete by accident when backspacing… this also means a triple click to edit is required to remove the selection of the block.
  5. love what anytype is doing, but it would be amazing to have a revert behaviours or legacy setting to keep updates but have an old school behaviour system (such as the upcoming collection 2.0 which looks incredible, but may change operation flows for existing knowledge capture)

I can’t open Anytype anymore since 0.55.1 and need urgent help because I’m traveling and do need Anytype on my desktop.

This morning I was about to write a joyful post here, seeing the many wonderful bug fixes and the update to the color palette that I appreciate a lot.

Then I also updated my new Mac and took it with me on a train trip. While at home everything worked fine, it now keeps crashing before opening the vault.

Please help, I urgently need to do work in the desktop App.

@UBr I suggest to deinstal Anytype and to install the version of your choice from here:

After that, you’ll need to input your pass phrase. After some minutes, everything should work again.

Thanks @Code-Jack . Unfortunately it didn’t work with 0.55.1. Still same crash “http response…” with modal “helper crashed.”

Should I try the version I had installed previously (0.54.11)? Or the alpha (0.55.1 alpha?)

Here’s the log — interestingly, at all the crashes, it shows "[2026-04-30 14:28:29.870] [info] [WindowManager].clearSavedTabs: Cleared saved tabs". But I never used tabs (I prefer side-by-side windows).


log tail:

2026-04-30 11:54:01.280] [info] Downloading update from Anytype-0.55.1-mac-x64.zip, Anytype-0.55.1-mac-arm64.zip, Anytype-0.55.1-mac-arm64.zip, Anytype-0.55.1-mac-arm64.zip, Anytype-0.55.1-mac-x64.dmg, Anytype-0.55.1-mac-x64.dmg, Anytype-0.55.1-mac-x64.dmg, Anytype-0.55.1-mac-arm64.dmg, Anytype-0.55.1-mac-arm64.dmg, Anytype-0.55.1-mac-arm64.dmg
[2026-04-30 11:54:01.281] [debug] Checking for macOS Rosetta environment
[2026-04-30 11:54:01.288] [info] Checked for macOS Rosetta environment (isRosetta=false)
[2026-04-30 11:54:01.288] [debug] Checking for arm64 in uname
[2026-04-30 11:54:01.291] [info] Checked ‘uname -a’: arm64=true
[2026-04-30 11:54:01.292] [debug] checkForUpdatesAndNotify called, downloadPromise is null
[2026-04-30 11:54:01.294] [info] Cached update sha512 checksum doesn’t match the latest available update. New update must be downloaded. Cached: tarTrF/qbO0C+nNbaKSuva0cGuRiIs3sP27kDsF4qLgXJzwVM9UX78s+Hqk2FJpHEZ5OzNECJ+aIvO8jfWQSGQ==, expected: GuqAjyffhiNKl8FB7Ut3Sh7IObfNGLRetgdvKBqBuAd1D2rqH6657bLI3W7kwPfxclVFpP02u9W92khBKnQHWw==. Directory for cached update will be cleaned
[2026-04-30 11:54:01.300] [info] Download block maps (old: “https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.54.11-mac-arm64.zip.blockmap”, new: https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.55.1-mac-arm64.zip.blockmap)
[2026-04-30 11:54:01.335] [error] Cannot download differentially, fallback to full download: Error: Cannot download “https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.55.1-mac-arm64.zip.blockmap”, status 403:
at ClientRequest. (/Applications/Anytype.app/Contents/Resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:209:34)
at ClientRequest.emit (node:events:519:28)
at SimpleURLLoaderWrapper. (node:electron/js2c/browser_init:2:124429)
at SimpleURLLoaderWrapper.emit (node:events:519:28)
[2026-04-30 11:54:02.418] [info] Download speed: 29895032 - Downloaded: 12.179515162763106% (29895032/245453383)
[2026-04-30 11:54:03.419] [info] Download speed: 31732050 - Downloaded: 25.868794808992305% (63495832/245453383)
[2026-04-30 11:54:04.420] [info] Download speed: 32325843 - Downloaded: 39.53589020201038% (97042180/245453383)
[2026-04-30 11:54:05.420] [info] Download speed: 32614139 - Downloaded: 53.17579428106721% (130521786/245453383)
[2026-04-30 11:54:06.421] [info] Download speed: 32797324 - Downloaded: 66.84976633628227% (164085013/245453383)
[2026-04-30 11:54:07.422] [info] Download speed: 32915335 - Downloaded: 80.5137295663185% (197623673/245453383)
[2026-04-30 11:54:08.422] [info] Download speed: 32997069 - Downloaded: 94.15697114266295% (231111471/245453383)
[2026-04-30 11:54:08.850] [info] Download speed: 33026559 - Downloaded: 100% (245453383/245453383)
[2026-04-30 11:54:08.853] [info] New version 0.55.1 has been downloaded to /Users/zio/Library/Caches/anytype-updater/pending/Anytype-0.55.1-mac-arm64.zip
[2026-04-30 11:54:09.003] [debug] Closing proxy server
[2026-04-30 11:54:09.006] [debug] Creating proxy server for native Squirrel.Mac (fileToProxy=https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.55.1-mac-arm64.zip)
[2026-04-30 11:54:09.007] [debug] Proxy server for native Squirrel.Mac is created (fileToProxy=https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.55.1-mac-arm64.zip)
[2026-04-30 11:54:09.010] [debug] Proxy server for native Squirrel.Mac is starting to listen (fileToProxy=https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.55.1-mac-arm64.zip)
[2026-04-30 11:54:09.012] [info] Proxy server for native Squirrel.Mac is closed (fileToProxy=https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.55.0-mac-arm64.zip)
[2026-04-30 11:54:09.014] [debug] Proxy server for native Squirrel.Mac is listening (address=http://127.0.0.1:58026, fileToProxy=https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.55.1-mac-arm64.zip)
[2026-04-30 11:54:09.025] [info] Update downloaded: {
“version”: “0.55.1”,
“files”: [
{
“url”: “Anytype-0.55.1-mac-x64.zip”,
“sha512”: “zSTkQ+EY2wBHCNU+SXAfYh9ljvUPj88l76HmQ6cmNzb+CskiaA6B0Ta7rWiX6hctxJ/7vkB4u3WNXwqT6c1SSw==”,
“size”: 258290799
},
{
“url”: “Anytype-0.55.1-mac-arm64.zip”,
“sha512”: “GuqAjyffhiNKl8FB7Ut3Sh7IObfNGLRetgdvKBqBuAd1D2rqH6657bLI3W7kwPfxclVFpP02u9W92khBKnQHWw==”,
“size”: 245453383
},
{
“url”: “Anytype-0.55.1-mac-arm64.zip”,
“sha512”: “GuqAjyffhiNKl8FB7Ut3Sh7IObfNGLRetgdvKBqBuAd1D2rqH6657bLI3W7kwPfxclVFpP02u9W92khBKnQHWw==”,
“size”: 245453383
},
{
“url”: “Anytype-0.55.1-mac-arm64.zip”,
“sha512”: “GuqAjyffhiNKl8FB7Ut3Sh7IObfNGLRetgdvKBqBuAd1D2rqH6657bLI3W7kwPfxclVFpP02u9W92khBKnQHWw==”,
“size”: 245453383
},
{
“url”: “Anytype-0.55.1-mac-x64.dmg”,
“sha512”: “dKd5ZB2B8qLkyXSTROPfcwqM5aSuyROHRJCIfEImfhcN4kWj58TcdDJN4l9uMxmdrvZRqm6+3AMczirt4OEiOw==”,
“size”: 264053952
},
{
“url”: “Anytype-0.55.1-mac-x64.dmg”,
“sha512”: “dKd5ZB2B8qLkyXSTROPfcwqM5aSuyROHRJCIfEImfhcN4kWj58TcdDJN4l9uMxmdrvZRqm6+3AMczirt4OEiOw==”,
“size”: 264053952
},
{
“url”: “Anytype-0.55.1-mac-x64.dmg”,
“sha512”: “dKd5ZB2B8qLkyXSTROPfcwqM5aSuyROHRJCIfEImfhcN4kWj58TcdDJN4l9uMxmdrvZRqm6+3AMczirt4OEiOw==”,
“size”: 264053952
},
{
“url”: “Anytype-0.55.1-mac-arm64.dmg”,
“sha512”: “fFHo/BJ1fH7BpCtyEP8DOWRi735O6GMaYuEdo8mhtpXJTIdQtEfaQVg5t9EV6RQlqT94AXEObAcFQYS0aySrbA==”,
“size”: 251143841
},
{
“url”: “Anytype-0.55.1-mac-arm64.dmg”,
“sha512”: “fFHo/BJ1fH7BpCtyEP8DOWRi735O6GMaYuEdo8mhtpXJTIdQtEfaQVg5t9EV6RQlqT94AXEObAcFQYS0aySrbA==”,
“size”: 251143841
},
{
“url”: “Anytype-0.55.1-mac-arm64.dmg”,
“sha512”: “fFHo/BJ1fH7BpCtyEP8DOWRi735O6GMaYuEdo8mhtpXJTIdQtEfaQVg5t9EV6RQlqT94AXEObAcFQYS0aySrbA==”,
“size”: 251143841
}
],
“path”: “Anytype-0.55.1-mac-x64.zip”,
“sha512”: “zSTkQ+EY2wBHCNU+SXAfYh9ljvUPj88l76HmQ6cmNzb+CskiaA6B0Ta7rWiX6hctxJ/7vkB4u3WNXwqT6c1SSw==”,
“releaseDate”: “2026-04-29T22:18:21.525Z”,
“downloadedFile”: “/Users/zio/Library/Caches/anytype-updater/pending/Anytype-0.55.1-mac-arm64.zip”
}
[2026-04-30 11:54:11.214] [info] [WindowManager].saveTabs: Saved 1 tabs, active index: 0
[2026-04-30 11:54:11.243] [info] [Api].exit, relaunch: true, isUpdate: true
[2026-04-30 11:54:12.634] [info] [Api].shutdown, relaunch: true, isUpdate: true
[2026-04-30 11:54:12.634] [info] Relaunch
[2026-04-30 11:54:12.752] [info] / requested
[2026-04-30 11:54:12.762] [info] /f7bd6f7b8e5b32465647723e37fd3680af5ce3d5e649423a6da6c81b28bdde14216d07630bebce3f70f58deea09a1a88959cc4e4e12faaa4a12f57b3704e538c.zip requested
[2026-04-30 11:54:12.762] [info] /f7bd6f7b8e5b32465647723e37fd3680af5ce3d5e649423a6da6c81b28bdde14216d07630bebce3f70f58deea09a1a88959cc4e4e12faaa4a12f57b3704e538c.zip requested by Squirrel.Mac, pipe /Users/zio/Library/Caches/anytype-updater/pending/Anytype-0.55.1-mac-arm64.zip
[2026-04-30 11:54:14.994] [debug] nativeUpdater.update-downloaded
[2026-04-30 11:54:15.043] [info] closeMain: true
[2026-04-30 11:54:15.043] [debug] Closing proxy server
[2026-04-30 11:54:15.043] [info] Proxy server for native Squirrel.Mac is closed (fileToProxy=https://anytype-release.fra1.digitaloceanspaces.com/Anytype-0.55.1-mac-arm64.zip)
[2026-04-30 11:54:15.052] [info] before-quit
[2026-04-30 11:54:22.993] [info] [WindowManager].loadAllWindows: Found legacy saved tabs
[2026-04-30 11:54:23.067] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 11:55:37.356] [info] [PowerMonitor] resume
[2026-04-30 12:47:04.783] [info] Checking for update
[2026-04-30 12:47:04.784] [info] Checking for update
[2026-04-30 12:47:04.798] [info] [PowerMonitor] resume
[2026-04-30 14:16:55.468] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 14:17:04.684] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 14:19:50.963] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 14:25:16.301] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 14:25:49.514] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 14:26:46.312] [info] [Window] render-process-gone: killed
[2026-04-30 14:28:29.870] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 14:36:19.490] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 14:52:30.028] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 15:03:40.450] [info] [WindowManager].clearSavedTabs: Cleared saved tabs
[2026-04-30 15:18:32.507] [info] [WindowManager].clearSavedTabs: Cleared saved tabs

Thank you for helping. Let’s continue in the bug report that I had previously submitted here.

Hi all @n7cgu4sxyjzl @Code-Jack @Astro-L @ogokcocoball — thanks for raising this, and apologies the change wasn’t well communicated in the release notes. Quick clarification, then I’d like your input.

Why this was added

To stop orphaned objects piling up after you archive a parent — pasted images, files, etc. that nobody links to anymore. Many users have asked for this over time. The behaviour is non-destructive: children are moved to the Bin, not deleted, with an Undo in the toast and a hierarchical view in the Bin so you can see what came from where. Fair point that it becomes effectively destructive if you don’t notice the toast and later empty the Bin - we need to improve this flow to decrease the chance of accidental removal.

What changed in 0.55.0

This behaviour already existed in earlier releases for images and files created inside a page. In 0.55.0 we extended it in two ways:

  • from just images/files to all objects — anything you create inside another object via the slash menu’s Create object action;
  • to files, images, and objects created inside Collections — which is exactly the case you’ve been flagging in this thread.

That’s the scope change behind the surprise here.

How the rule works today

A child is cascaded only if both:

  1. It was created through a parent — as a block on a page, inside a Collection, or via a property — i.e. not at root level via the global “New” button.
  2. It has no other active backlinks.

This is tracked by a Created in context property that’s currently hidden. We’ll unhide it — the invisibility is the main reason the rule feels unpredictable.

@n7cgu4sxyjzl — the Origin = Drag’n’Drop pattern you noticed is a side effect of this rule, not the cause: dragging into a Collection sets that Collection as the creation context, so those images cascade; images created elsewhere and later added to the collection don’t.

Where we’d like your help

The core question is where the parent → child hierarchy feels natural, and where it doesn’t.

For blocks it seems clear-cut: an image you created inside a page is intuitively part of that page. For Collections, this thread suggests the opposite — a Collection feels more like a curated list of independent objects. Properties sit somewhere in between.

We’re leaning toward always asking for confirmation when cascade is about to happen — it’s the simplest rule and keeps you in control — but a per-container rule is also on the table.

A few quick scenarios — your answers will shape what ships next:

  1. Page with pasted images, then archive the page → cascade to Bin, or leave images in library?
  2. Object with an image as a property/cover, then archive the object → same question.
  3. Collection with added objects, then archive the Collection → cascade, or leave objects?
  4. Confirmation dialog every cascade, or only for some containers (which)?

Thanks for the engagement!

I’ve had 150% set for every type and it still works if you set a default template width at 150%. But there’s an annoying red mark now on every object with “This object has layout settings that differ from the type” because it’s either 100% or 200% at type level. Probably the default template’s settings should have a priority.

Thanks for the explanation! Based on my usage patterns, it sounds like I’ll rarely encounter the cascades you described, so my feedback may not be the most relevant. But my first reaction is to go for #4 (every cascade). As I said above, I don’t mind cascading binning in concept, and I can imagine it being useful if I want to get rid of a bunch of stuff efficiently. I just want to know it’s happening before it does.

[EDIT:] Also I’ll add that the bin/not-bit logic you described does make a kind of sense, but in practice I wouldn’t expect users to remember how they made every object and correctly anticipate how that will apply when they bin a parent. Note how before you gave that explanation, people had inferred that it was just based on orphaning. I think orphaning actually makes the most sense. It would seem reasonable and understandable to me if when I binned an object, I got a pop-up saying something like, “This contains some objects that aren’t contained by anything else. Would you like those to go in the bin too?”

such a biggest improvement, putting you way closer to the cloud competitors!!!

so helpful! honestly this feels like you are really listening to feedback - much appreciated :heart:


damn, the quality of life improvements hit HARD this time! thank you!!!