The honest view from inside technical leadership
Video · Excerpt

From the CTO chair

Conversations and reporting with the people building and governing technology.

Excerpt · AI & Engineering

JPMorgan CEO Warned About AI Agents. This Is Why.

Dr. Miquel Noguer i Alonso — Co-founder & Chief Science Officer, AIFI

· 6 min 36 sec

What changes when an outside AI agent can move your money?

Reading an account balance and initiating a transaction are different grants of authority. A customer may want help understanding their finances without authorising a system to sell investments, send a payment or change a beneficiary.

In this excerpt, Dr. Miquel Noguer i Alonso and I discuss outside AI agents in banking, unintended financial decisions and the boundaries needed around tools that can act on a customer's behalf. Miquel is co-founder and Chief Science Officer of the Artificial Intelligence Finance Institute.

The JPMorgan warning provides the video's framing. Jamie Dimon is not a guest in this conversation; Miquel is. The complete discussion is available in AI Finance Expert Warns: Don't Give AI Access to Your Money Yet!.

Permission to help is not a complete transaction specification

Consider a hypothetical request to make better use of idle cash. Selling a portfolio, changing an allocation and transferring a small balance could each be presented as ways to satisfy that request. They have very different consequences.

The engineering question is how the system narrows an ambiguous instruction into an action a customer actually approves. The clip's published description raises examples such as an unintended portfolio sale or transfer. These are scenarios for examining the controls, not reports of losses suffered by a named customer.

Define the action before asking for approval

My practical interpretation is that a transaction approval should specify the account, action, amount, recipient or instrument and relevant limits. A confirmation screen that says only “continue” gives the customer little evidence of what the system will do next.

CapabilityBoundary to make explicit
Read account informationWhich accounts and which data are accessible
Prepare a transactionWhether preparing a proposal can itself change anything
Execute an approved actionExactly which action the approval covers
Repeat or retryHow duplicate execution is prevented
Escalate an exceptionWho receives it and whether execution waits

This table is an editorial design checklist, not a description of JPMorgan's implementation or a control framework endorsed by the guest.

Supervision needs evidence

A bank or customer reviewing an agent's action needs a record of the instruction, the authority granted, the tool calls and the resulting transaction state. Otherwise, a plausible explanation after the event can obscure a mismatch between intent and execution.

Unusual-transaction detection adds another layer, but it does not answer every authorisation question. An action can look statistically ordinary while being something the customer never requested.

Who is responsible if the agent makes a mistake?

That question is a central topic of the conversation, not a settled conclusion on this page. The responsibility of a customer, bank, agent provider or other party depends on the arrangement and applicable rules. The useful engineering response is to preserve the evidence needed to examine the decision rather than assume responsibility has automatically moved to someone else.

FAQ

Is Jamie Dimon interviewed in this video? No. The guest is Dr. Miquel Noguer i Alonso. The video uses the JPMorgan warning as context for the discussion.

Is this the complete conversation? No. This is a six-minute excerpt. The full interview runs approximately 75 minutes.

Does connecting an agent to an account mean it should be able to transact? Reading data, preparing a proposal and executing a transaction should be treated as separate capabilities. The precise controls depend on the product and the authority the customer intends to grant.

Guest and related material

Hosted by Himanshu Saxena, Diary of a CTO. These notes discuss engineering and governance; they do not provide investment advice or determine legal liability.

Featured in this conversation

Host: Himanshu Saxena

← All episodes and videos