As part of testing
@Muse, I quizzed it to explain to me a few things I think about when using these agents and deciding how much connections and context to give - the struggle of the Trust-Utility Curve (the more you give, the more useful it can be).
nitter.siddz.com/melodykoh/status/20262…
TLDR - there continues to be limitations around how LLMs fundamentally work and the probabilistic nature of things, and there really isn't a way to get around on context leakage or prompt injection-like attacks. However, I found Muse/Meta's willingness to be transparent in its mechanics reassuring.
A few highlights on my Q&A with Muse - see more details on the screenshots of my questions and its responses. 🧵
Q1 - you say that you will ask for my permission for actions, but how do I know this can be enforced deterministically (vs instructions in files, which are just vibes for these models)?
Most reassuring part of the answer:
"When I invoke a send tool, the runtime intercepts the call and blocks execution until you've approved it. I can't trigger the approval myself, can't see it, can't override it — the approval card is invisible to me and your decision is final. So even a compromised or injected version of me, actively trying to send without asking, hits the same wall: there is no code path where the send executes without the runtime obtaining your decision first."
Translate to non-developer speak: there's a mechanical gate that forces the model to serve up approval to the user when the action is a list of predefined "must get user approval". No vibes-bsed (good!)
Finally caved in to try Muse. Quick hits / thoughts thus far (especially compared to Instinct)-
1. I really like the ability to see the detailed actions (tool calls, steps) behind the scene - they do a good job hiding these but they’re also easily accessible and not completely black-box / headless. Why is it useful? It’s a level of transparency and also lets me intercept if I see the agent going down the wrong path
E.g. I asked it to draft something for me and it found a GitHub public repo on content by itself. I saw it (good job finding it!) and had to intercept and tell it that the content there is few months behind my private repo, so don’t use that as authority
2. The app interface allows for much more robust interaction modalities. I especially like how you can see browser use actions (like literally what it’s doing on the browser) and you can take over at any time.
In contrast, having used Instinct for a few weeks now, the single-threading iMessage interface is a bit unwieldy and hard to manage, especially when having it do multiple tasks and needing to find stuff from earlier conversations
More to come. Only 30mins in!