App Mounting Pattern
Local space mounting
Standalone app server, referenced by the mount resource
Option 3 is supporting both mounting patterns
Local Only Agents and Apps
When do you want a local app?
You want it to work offline
You don't want to share some secrets with a server
It sounds like we don't need local apps, for now!
Apps and Agents Permission
We want permissions to be driven by normal hypermedia caps, regardless of mounting pattern
If you can:
write to a space (mount resource)
the server is configured to do so,
Then the app will be instantiated and mounted!
SSO Enterprise Requirement
Probably a vault sign-in workflow
Anthropic API SSO, Google/Gemini maybe too?!
Fine-Grained Permissions
You can't be granted access to part of a resource. Design your resources so that privacy permissions are partitioned
Broken Cmd-A in most text inputs
@Untitled Contact will fix some of these
New Agent Workflow
Ion Notifs in Discord
Ion will now send STT updates to #dev-notifs channel
Cross-Vault Identity Project
In the EE, there is a desire to have shared identities. Lets wait for keyline project to complete, and we can clean up the EE privacy features
Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime
