Bug Report: Multi-Space API Access Not Working
WHAT IS THE BUG
When an AI agent (Bobrik) accepts space invite links for multiple Anytype spaces, the local API endpoint only exposes the single space it was originally launched with. Accepting invites to additional spaces (Personal, Work) succeeds at the network/identity level, but the API cannot query, search, or retrieve objects from those additional spaces. All API calls silently return empty results or only return data from the originally configured space.
HOW TO REPRODUCE IT
-
Set up an AI agent (e.g. Bobrik) with API access to one Anytype space
-
From a second Anytype space, go to Space Settings > Members > Invite
-
Generate an invite link and share it with the agent
-
Agent calls acceptInvite(inviteURL) — returns success with the new spaceId
-
Attempt to call any API method (e.g. getTypes(), search(), getObjects()) using the new spaceId
-
See empty results — the API only returns data from the original space
THE EXPECTED BEHAVIOR
After successfully accepting a space invite, the API should be able to query all spaces the agent is a member of — either by switching space context via a parameter, or by exposing a multi-space endpoint. The invite acceptance should translate into actual API-level access, not just network-level membership.
ADDITIONAL CONTEXT
-
The invite acceptance flow itself works and returns a valid spaceId
-
The limitation only becomes apparent when trying to actually use that spaceId with API calls
-
There is no documented way to switch space context in the local API, nor any error message indicating the limitation — calls simply return empty results, which is misleading
-
This makes it impossible for agents to work across a user’s Personal and Work spaces even after being explicitly invited
TECHNICAL INFORMATION
-
Setup: Anytype local API running at 127.0.0.1:35627
-
Agent: Bobrik AI assistant
-
Spaces affected: Personal space, Work space (both joined via invite link)
-
Original space: accessible and fully functional
-
Desktop: 0.55.4