WishD

Wishd is a browser self-evolving agent for DeFi.

Type you intent, e.g. "swap 0.001 ETH for USDC" or "lend 50 USDC on Compound"or choose pre-built intents in Composer pills — and it picks the right widget, fetches the quote, prepares the bundle. You sign in your own wallet.

No CLI, no skills to write, no agent wallet holding your money.

Scheduled tasks and execution layer is built with KeeperHub. When something should run on a schedule — auto-compound, DCA — the agent recommends a KeeperHub workflow and scopes a Porto session-key for it: which token, how much, until when. You grant it once. The workflow runs deterministically in KeeperHub. Deployment is made via KeeperHub MCP. In future you it will be possible to describe, create and edit workflows in plain English

The core is a Next.js 15 app with a Claude Agent SDK loop running on the server.

Instead of the agent returning text that the frontend then has to interpret, it emits a typed event stream over SSE — tool.call, chat.delta, widget.render, widget.patch — and the browser is more or less a renderer for whatever the agent decides to show.

The page you see is whatever widget the agent rendered last. To make that work, every protocol lives in its own folder under plugins/ exporting an intent schema, a prepare() function, and a widget component. The agent loads them at boot, and adding a new one is dropping in a folder. Keepers follow the same shape.

For swaps we use the Uniswap Trading API on mainnet and the L2s it covers. The Trading API doesn't reach Sepolia, though, and most of our demo runs there, so on testnet we fall back to the V3 contracts directly (QuoterV2 for pricing, SwapRouter02 for execution) and prepend the ERC-20 approval as an extra call inside the Porto bundle — so even with the workaround the user still only signs once.

The wallet layer is Porto, which gave us account abstraction and session-keys for free. The interesting part there is automations: when the agent recommends a recurring workflow (auto-compound, DCA), it calls into KeeperHub over MCP, and KeeperHub asks the user to grant a scoped Porto session-key — token, spend cap, expiry — through a delegation modal.

We actually forked KeeperHub for this and added a Porto plugin so workflows could request and consume those delegations cleanly; that fork is live at kh.sumula.online. The result is that the agent never holds funds and never signs at runtime: it prepares, the user signs once, KeeperHub executes deterministically from there.

The piece I'm most fond of is widget.patch. Because widgets are mounted from SSE events, the agent can patch a widget that's already on screen — a quote refreshes without unmount, the swap card visibly "fills in" as tool calls return, the activity sidebar tails the same stream and shows the agent's tool log live.