127 karma · joined February 27, 2019
Email: jaredlmosley@gmail.com
linkedin.com/in/jaredlmosley
It makes it harder for the LLM to understand what’s going on, not easier.
I’ve been wrapping the agent’s curl calls in a small cli that handles the auth but I’m wondering if other people have come up with something lighter/more portable.
This lets me add quick skills that are essentially just: “this is the OAS link, this is how you store and use the authorization, this is when I want you to use it”. That combined with pointing it at the documentation for common workflows and usage examples, and it’s been great.
The only thing I’ve had trouble with is auth really. MCPs are treated as first class citizens by most model provider’s agents and trying to provide a shell-based alternative for hiding the secret credentials from the LLM has been difficult.
I feel like this is why drugs can sometimes help with creative things, especially if you're familiar with the drug, as long as you can harness this decontextualization to put more of your focus on one thing, kind of like clearing your mind. However, its usually fruitless/harmful in anything requiring complex reasoning/judgement because it is reducing your ability to see the big picture.
There should be regulations on existing products (and similar products released later) as they exist and you know what you’re applying regulations to.
I don’t get this perspective. The first planes, cars, computers, etc. weren’t initially made with safety in mind. They were all regulated after the fact and successfully made safer.
How can you even design safety into something if it doesn’t exist yet? You’d have ended up with a plane where everyone sat on the wings with a parachute strapped on if you designed them with safety first instead of letting them evolve naturally and regulating the resulting designs.