Loading video...
Video Failed to Load
IBKR for Claude Code. Project:VEX gives coding agents like Claude Code and Codex the tools to swap tokens, bridge funds and trade perpetuals. Your keys stay on your machine, and execution follows your permissions. Live on Virtuals Protocol.
15,584 views • 2 days ago •via X (Twitter)
19 Comments

Faster 🟦

@ProjectVEXai Keeping keys on the user's machine while execution follows set permissions is a sound design. The permission layer is the actual product, because scoped limits per asset, venue and size are what let someone hand an agent capital without watching every trade.

@ProjectVEXai claude code being able to swap and trade, keys still on the laptop, is the version I wanted to click around. how does the permission show up for the person? one approval each time, or a standing limit?

@ProjectVEXai VOTED!

@ProjectVEXai my options bot lets the AI pick the trade but never touch the broker. claude code with perps access is how you learn why lmao

@ProjectVEXai That execution is tethered to permission sets. interesting new trust model for AI agents!

@ProjectVEXai $VEX ☁️🟦

@ProjectVEXai Keys local, permissions enforced, agents executing. this is the right architecture for the era

@ProjectVEXai Vex on Top...

@ProjectVEXai @ProjectVEXai's execution model assumes local key custody solves agent trust. We'd treat that as only half the problem. Without verifiable behavior history, you're still trusting a fresh agent instance with your permissions.

@ProjectVEXai Vex it 💙

@ProjectVEXai This looks like a great tool for coding agents

@desu_vex @ProjectVEXai VEX IT!

@ProjectVEXai Trading agents need verified permissions and contract checks before any swap or bridge. Pre-execution verification catches mismatches early.

@ProjectVEXai $prxvt bro

@ProjectVEXai agents trading perps with your keys local is next level stuff

@ProjectVEXai The agents that execute instead of wait are the ones that win. This is where it all goes next.

@ProjectVEXai Big Alpha on Virtuals

@ProjectVEXai The part that actually matters is execution following permissions. Agents that can swap and bridge are useful only when a hard scope stops a bad loop from becoming a drained wallet.
