How do you enforce this? You have a system where the agent can email people, but cannot email "too many people" without a password?

▲

jameslk 4 hours ago | parent [-]

It's not a perfect security model. Between the friction and all caps instructions the model sees, it's a balance between risk and simplicity, or maybe risk and sanity. There's ways I can imagine the concept can be hardened, e.g. with a server layer in between that checks for things like dangerous actions or enforces rate limiting

	▲	sowbug 3 hours ago \| parent \| next [-]
		If I were the CEO of a place like Plaid, I'd be working night and day expanding my offerings to include a safe, policy-driven API layer between the client and financial services.
	▲	chongli 3 hours ago \| parent \| prev [-]
		What if instead of allowing the agent to act directly, it writes a simple high-level recipe or script that you can accept (and run) or reject? It should be very high level and declarative, but with the ability to drill down on each of the steps to see what's going on under the covers?