Skip to main content
Start with the boundary that owns the behavior you want to change. An identity edit, a new tool, and a new rendering surface are different kinds of extension.

​
Build a complete capability

For a new spatial action, define the input schema, route it through the protocol, implement the visible effect, and return a useful result when prerequisites are missing. Test the actual boundary where errors occur. Prefer a small operation with clear inputs and results over a broad tool that silently guesses at execution, permissions, or surface support. Let the model compose those operations into a larger task.

​
Preserve continuity

Keep identity and conversational memory with the Entity. Surfaces and shells should present and interact with that state rather than quietly maintaining a second version of it. The shipped engine has explicit provider and surface boundaries, but it is not yet a universal plug-and-play adapter for every external agent harness. Integrating a different harness requires implementing and testing the appropriate protocol and lifecycle behavior. Continue with tools, social surfaces, spatial protocol, or portable Entities.