Feedback for Anytype Team
Reported by: hansamann (Sven Haiges)
Date: 2026-06-10

Issue: Multi-space API access not working via invite

What happened

Bobrik (AI assistant) was invited to two additional spaces via invite links: Personal and Work
Invite links were accepted successfully (acceptInvite returned success with spaceId + spaceName)
However, anytypeHelper (the local API client at 127.0.0.1:35627) can only query the one space it was originally launched with
Querying Personal or Work space IDs returns empty results — the API does not switch context between spaces

Expected behaviour

After accepting a space invite, the agent should be able to query objects, types, and properties in that space — e.g. anytypeHelper.getTypes() scoped to Personal should return types from Personal.

Actual behaviour

All API calls return results from the single "boot" space only. The other space IDs are ignored or return empty.

User impact

User has cycling Activities and other content in their Personal space that the agent cannot access or read, despite being a member of that space.

Suggested improvement

Either:
1.
Allow the local API to switch active space by spaceId parameter
2.
Expose a multi-space query endpoint
3.
Document that agents can only access the space they were originally configured for, so users know to set this up correctly

Steps to reproduce

1.
Configure Bobrik in Space A
2.
Send an invite link for Space B
3.
Agent calls acceptInvite(url) — returns success
4.
Agent calls anytypeHelper.getTypes() with Space B's ID — returns empty or Space A results