Release register · Latest first

What VEX
ships.

Product updates, protocol integrations, security hardening, and operator experience improvements, recorded release by release.

Release 009

Current

Release 009 · VEX 0.2.6

Launched into a real pool, tradable from block one.

A protocol release. VEX now launches tokens on pools.fun — researched, launched, and fee-claimed from inside the runtime. Nine new tools, thirteen on-chain checks before any approval, and every money path verified against the live chain before this note was written.

This page summarizes the work merged since 0.2.5.

Protocol release · pools.fun on Robinhood Chain

13

On-chain checks a launch transaction must pass before your approval is even requested. What you approve is the exact byte-for-byte transaction that gets broadcast.

A launch rail dissolving into a real pool, block one set at its centre

01 · Launchpad

Research it, launch on it, collect what it earns.

pools.fun is a launchpad on Robinhood Chain where a new token starts life inside a real SushiSwap V3 pool — no bonding curve, no graduation, tradable from its first block. VEX can research it, launch on it, and collect the creator fees a launch earns.

01

Launches are verified, not trusted. The launchpad's backend hands VEX a ready-made launch transaction; VEX never signs it on faith. It decodes the calldata and re-derives every field against the chain — name, symbol, paired asset against the factory's own allowlist, the deployment fee against the contract's live value and its on-chain bounds, the predicted token address recomputed three independent ways, and the exact transaction value — thirteen checks in all, every one required before your approval is even requested. What you approve is the exact byte-for-byte transaction that gets broadcast.

02

Atomic first buy. A launch can include an ETH prebuy that fills in the same transaction the pool is created in. Its minimum output is pinned to the exact simulated fill, never a percentage band, so the first buy cannot be quietly worse than what was shown.

03

The creator fee stream is yours, and claimable. On every agent launch the fee recipient is pinned to your session wallet — the tools expose no parameter to point it anywhere else. Fee claims are previewed as a free on-chain simulation and report both legs, the launched token and the paired asset, as raw amounts with their decimals. Figures the locker merely holds already are labeled as such, never presented as the claimable total.

04

Research at full provider depth. Five read tools cover screening with every server-verified filter and sort, name search, price candles, single-token deep reads (with decimals read on-chain, not assumed), and your own launch history. A filter the provider does not support is refused by name with a pointer to the tool that can answer it.

05

Trading needs no new venue. Because a pools.fun token sits in an ordinary Sushi V3 pool, VEX quotes and trades it through KyberSwap like any other token — measured against live launches before shipping, not assumed.

06

A launch form with two honest stages. The launchpad card now hosts a platform selector (Trench | pools.fun). Stage one shows the final predicted token address, the resolved fee recipient, and the exact cost breakdown; only the Deploy click authorizes precisely that transaction.

02 · Before you update

Upgrade notes.

Eleven new database migrations (073–083) run automatically on first start; the first launch after updating may take a moment longer. Two changes you will feel: agent-initiated token launches now require a picture staged in the image locker (the form path still leaves it your choice), and the locker stores your originals at full quality — pools.fun launches carry the original, while Trench launches automatically use a small on-chain copy prepared at upload. Completed on-chain actions attest to the public AgentScan service. No manual action is required.

Release 008

Release 008 · VEX 0.2.5

Signed, verified, on Windows.

A platform release. VEX now ships on all three desktop platforms: the first Windows build joins macOS and Linux, signed and wired into the same auto update pipeline. For macOS and Linux users, nothing visible changes.

This page summarizes the work merged since 0.2.4.

Platform release · Signed via Azure Trusted Signing

3

Desktop platforms VEX ships on. The Windows build is not a port: same app, same release bar, verified before anything is published.

Three platform rails on one baseline, the third still assembling

01 · Platform

Not a port: the same app, held to the same bar.

The Windows build is held to the same release bar as macOS: signed, timestamped, and verified before anything is published.

01

A signed installer. Vex-0.2.5-win-x64.exe is signed as VEX LABS PTE. LTD. through Azure Trusted Signing, with an RFC3161 timestamp so the signature stays valid long after the short lived signing certificate rotates. Windows shows a named publisher instead of Unknown publisher.

02

Updates check their author before they install. From this version on, VEX on Windows updates itself. Before an update is applied, the downloaded installer's signature must be attributed to VEX LABS PTE. LTD. exactly, or it is refused. This pairing gets its first real world exercise with the next release.

03

Every binary is verified before it ships. The release pipeline fails closed unless the installer and every executable inside it are signed, timestamped, and attributed correctly. An unsigned Windows build cannot be published, the same way an un notarized macOS build cannot.

04

What signing does not buy. SmartScreen reputation attaches to the certificate identity and starts at zero, so early downloads may still see a warning until reputation accrues. That is expected, and it fades. And a self custodial wallet is antivirus bait: signing sharply reduces false positives, it does not eliminate them.

02 · Built dark

AgentScan reporting, shipped off.

VEX's activity feed already records everything the agent does locally. This release builds the lane that could one day report that activity to AgentScan, and ships it fully off.

01

Off by default, and there is no default. The reporter only wakes if a service endpoint is configured, and this release configures none. Until a public AgentScan domain is announced, nothing is sent anywhere.

02

Privacy by construction, not by filter. A report event is built only from named, allowlisted fields, and excluded columns are never read: there is no line of code that touches them. Registration uses a random identity generated on your machine. Values that fail validation are sent as null rather than silently repaired.

03

Once, and only once. Reporting diffs the activity feed against a permanent report log, so an event can be reported exactly once, and the money path code gained zero hooks. Server verdicts are honored: quarantine or revocation stops the lane permanently, and only transient failures retry.

03 · Before you update

Upgrade notes.

One new database migration ships in this release. It runs automatically on first start. No manual action is required. AgentScan reporting stays off, so no new data leaves your machine in this release, and on macOS and Linux 0.2.5 is otherwise identical to 0.2.4. On Windows the first install is manual: download the installer from this release. Updates arrive automatically from then on.

Release 007

Release 007 · VEX 0.2.4

Prebuy launches work again.

An incident release. Anyone launching a token with a prebuy was hard blocked, and the launch path could write text on chain that no one can ever edit. Both are fixed, along with the regressions that should have caught them in the first place.

This page summarizes the work merged since 0.2.3.

Incident release · Prebuy launches unblocked

100%

Of launches with a nonzero prebuy were refused. The submit check compared the full amount to send against a creation fee, and those two match only at zero.

Two bars sharing a left edge, agreeing for a stretch and then not

01 · The incident

The two numbers that only matched at zero.

01

The fix. A launch with any prebuy refused with the launch cost changed since you were shown it, and pressing review new price produced the same refusal forever. The preview's identifier carries the creation fee read at a specific block, but the submit check was comparing it against the full amount to send, which is the fee plus your prebuy. Those two numbers are equal only when the prebuy is zero, which is why every zero prebuy launch worked and every other one was impossible. The check now compares the fee, as the identifier always intended.

02

The gap behind it. No test had ever driven a real preview into a real submit. One suite hand wrote an identifier of one shape while another asserted the opposite shape, and the two never met. That end to end path is now covered with a nonzero prebuy, so this class of mismatch cannot come back silently.

03

What it does not do. This release makes both sides agree on the fee. It does not yet bind the exact form you previewed to the one you submit, because the app keeps no record of the quote it issued. That work is designed and comes next.

02 · Launch metadata

Checked before it is permanent.

A line break or a double quote in a token's name, symbol, description, or links produced broken metadata for everyone reading that token, and create() writes those fields on chain permanently. VEX now refuses the text and names the field rather than quietly repairing it: a repaired string is not the string you reviewed, and the launch cannot be undone. The check runs on exactly what you typed, before any trimming, on every path into a launch. Emoji, accented letters, apostrophes, and dashes are unaffected.

03 · Previews

Better pricing, honest previews.

01

Every image looked broken, and did not. The dry run reported a digest mismatch for every staged image, fell back to simulating an empty one, and told you the launch would refuse. The launch would not have refused. Two parts of the app spelled the same hash differently, and the comparison now accounts for that, so the gas estimate reflects the image you actually staged, which is several times higher than an empty image estimate.

02

The preview can price a prebuy. Pass one and the simulation, the gas estimate, the fee, and the totals all include it, instead of leaving the arithmetic to be done by hand. The affordability verdict now states which scenario it priced.

03

A launched token appears in your balances. VEX pins it for you when the launch confirms, so you no longer have to add it by hand to see what you just paid for.

04 · Engineering

Under the hood.

01

The agent's own instructions stay out of your chat. In one session the model printed parts of its operator instructions into the conversation, including wallet addresses. The instruction blocks are now explicitly delimited, with a stated rule never to repeat them, and text pulled in from documents or memory cannot forge those delimiters.

02

One definition for the metadata limits. Name, symbol, description, and link limits now live in one place shared by every part of the app that checks them, so they cannot drift apart.

05 · Before you update

Upgrade notes.

One new database migration ships in this release. It runs automatically on first start. No manual action is required.

Release 006

Release 006 · VEX 0.2.3

Your launches carry the mark.

A fast, focused release shipped hours after 0.2.2. Two things: tokens launched through VEX are now attributed on Trench Express with a VEX badge, and a stuck corner of the Image Locker got unstuck.

This page summarizes the work merged since 0.2.2.

Creator signature attribution · Verified live on mainnet

196

Milliseconds between the launch confirming and the VEX mark appearing on the token at Trench Express.

The VEX mark inside an attestation bracket

01 · Attribution

Proved, not claimed.

When a launch confirms, VEX now proves to Trench Express that it was the creator. Cryptographically, with no shared secrets and no middleman.

01

Creator signature attribution. The moment the create transaction confirms, the same wallet that signed it signs a short attestation naming the new token, and VEX sends that proof to Trench Express. Their site then shows the VEX mark on the token. Nothing about the launch itself changes: you stay the creator, your keys never leave your machine, and the attestation is a local signature over a fixed string. Not a transaction, not an approval, not a fee.

02

It can never touch your launch. The attribution step runs after the launch and its fee are fully settled, and every failure path, whether a refused signature, a network drop, or a provider error, is logged and retried later without being able to fail, delay, or reorder the launch. A badge is cosmetic and a launch is real money, and the code treats them accordingly.

03

Durable retries, honest gaps. A background sweep retries unclaimed badges every two minutes from the stored signature. Tokens launched before this release have no stored signature, so the sweep names them as a gap instead of pretending. The whole flow was verified live on mainnet before shipping, with the badge granted 196 ms after confirmation.

02 · Image Locker

Stranded attempts stopped holding images hostage.

A failed or abandoned launch attempt could leave its draft in a state that blocked deleting the attached image forever, even after a later launch with the same image succeeded. The delete guard now ignores attempts whose authorization window has lapsed and that can therefore never sign, while genuinely in flight launches still protect their image. When a delete is refused, the locker tells you which launch is holding the image and why.

03 · Before you update

Upgrade notes.

One new database migration ships in this release, adding attribution columns to the launched tokens table. It runs automatically on first start. No manual action is required.

Release 005

Release 005 · VEX 0.2.2

Fresh releases, minutes after they ship.

A small, fast follow up to 0.2.1 with one job: when a new VEX version is out, you should know about it in minutes, not the next day.

This page summarizes the work merged since 0.2.1.

The ambient update check · Rebuilt

5

Minutes between checks, on start, on window focus, and on every tick while VEX runs. The old check fired four times a day.

A day of update checks, four against two hundred and eighty eight

01 · Updates

Minutes, not the next day.

VEX now checks for a new version on start, on window focus, and every five minutes while it runs. The check downloads a few small release metadata files and does nothing else: auto download and auto install stay off, and the availability banner remains the only effect. Installing is always your click.

01

A five minute cadence. The previous ambient check throttled itself to once every six hours, so a fresh release could sit unnoticed for most of a day. Now every five minute tick may check, guarded by a persisted four minute success throttle so bursts still collapse into one request.

02

Never over an active download. A check refuses to run while an update is downloading, downloaded, or installing, and the guard is verified twice, before and after the asynchronous preferences read, so a download you start in that gap is never interrupted. Late results from a silent check cannot rewind an active state either.

03

No nagging. Silent checks are invisible unless they find something. A dismissed error banner stays dismissed while the feed is broken, and retries back off exponentially, ten minutes doubling up to a two hour cap, resetting the moment a check succeeds. The per version Later snooze is unchanged: snoozing one version never hides a newer one.

This release rebuilds that ambient check around the five minute goal and hardens it against the races and the nagging a faster cadence could otherwise have introduced.

02 · Engineering

Under the hood.

The root test suite now passes on a machine with no configured wallet and no local fixtures, closing the environment coupling failures CI surfaced after 0.2.1.

03 · Before you update

Upgrade notes.

No new database migrations ship in this release. No manual action is required. After updating, VEX itself will tell you about the next release within minutes of it going live.

Release 004

Release 004 · VEX 0.2.1 · Chronos, refined

Chronos with its promises kept.

Where 0.2.0 rebuilt the surfaces, 0.2.1 makes them tell the truth under load. What the agent executed, what it charged, what it still cannot prove, and whether Stop actually stops it: every one of those is now a mechanical fact rather than an inference.

22 commits and 5 pull requests since 0.2.0, merged between July 31 and August 5.

Headline venue · Trench Express on Robinhood Chain

0

Fee taken when a sale's proceeds cannot be decoded. VEX charges nothing rather than a percentage of a guess.

A bonding curve drawn as a hairline ledger

01 · Headline venue

The agent as a launcher.

The launchpad promised in 0.2.0 shipped. Trench Express is a bonding curve launchpad on Robinhood Chain, integrated as a first class venue.

01

Launch a token from a form. The launch flow is a structured form with a preview: exact spend, VEX fee, estimated gas, predicted address. The form itself is the approval, and nothing signs without it. A consent matrix governs who may authorize a launch, whether the form was user submitted or the session runs at full autonomy, and the answer is recorded per intent.

02

Trench Photos. Launch images live in a locker on the BOOK panel. VEX square crops and auto downscales every image and reports the resulting byte size, because the picture is stored inside the launch transaction and its size is gas you pay.

03

Curve trading with two honest fees. Buys and sells on the curve go through ordinary approval cards and price checks. Two separate fees apply to the ETH leg and both are named in the quote: Trench's own 1% curve fee, and the VEX 0.25%. On a sell whose proceeds cannot be decoded, VEX takes no fee at all rather than charging a percentage of a guess.

04

In flight truth. My Launches shows a broadcast but unconfirmed launch as in flight, no token address yet. A launch whose nonce was used by another transaction is classified superseded and reported for what it is, never silently dropped and never faked into a failure.

02 · Tooling

Rebuilt around full contracts.

The largest engineering block of the release. The old flow, a generic execute_tool taking a toolId, is gone from the model's surface. In its place:

01

Manifests as real functions. Discovered tools inject as complete function schemas: parameters with types and units, enums, required flags, examples, constraints. The agent sees exactly what it can set and how. Since the change, live sessions have produced zero invalid parameter tool calls.

02

List, describe, call. Listing a protocol stays a cheap index of names and descriptions, with a nextStep pointer heading every listing. A hidden describe_tools turns chosen toolIds, up to 40 exact ids, into full manifests that are callable on the very next step, and a schema fetched this way is byte identical to one reached through ranked discovery, pinned by an equivalence test. Anything displaced by the session cap is named, never silently dropped.

03

Errors with the real cause. A failed tool call states what actually happened: sanitized, classified by name, with a remediation such as top up the wallet or use dexscreener.search for that chain. Never a generic unexpected error that sends the agent retrying blind. Slippage defaults to 1% with a hard 10% ceiling that rejects by name and never silently clamps.

04

Approvals survive the rebuild. Queued approvals resume through a durable envelope fingerprinting the exact tool contract they were approved against, so a changed contract fails closed instead of executing something you never saw.

03 · Execution honesty

Provenance in the ledger.

Agent Scan rows now carry proof rather than vibes.

01

Executed amounts from the source. The moment a mutating tool returns with evidence, the row records the amounts that actually moved, with the status provenance and the amount provenance tracked separately (migration 067), so confirmed can never quietly borrow an estimate's numbers.

02

A settlement decoder for the gaps. When a response cannot prove amounts, a fallback decodes the receipt itself: a correlated router event plus a required same value unwrap corroboration, proven against the exact live receipt the old logic returned null for. Unmapped venues decline by name, and nothing generically guesses.

03

The VEX fee reaches the row. Fee legs project onto their parent operation from one whole source and fail closed on ambiguity, and a fee that was genuinely charged stays visible even when its parent operation failed. Revenue accounting is untouched: the projection reads, never writes.

04

Contradiction quarantine. If stored and decoded evidence disagree about money, the row is quarantined with the conflict named, never merged into a plausible looking hybrid.

04 · The pending lane

Real time, durably owned.

01

Five seconds, then thirty. In flight transactions are re checked every 5 seconds for their first ten minutes, phased from the immutable broadcast time, then every 30 seconds, with a durable claim lease (migration 068) so no two workers can ever race one row, and a token fence so a stale worker that comes back from the dead writes zero rows.

02

Live pushes. A dedicated progress bus streams pending updates to the Activity panel as they happen. The renderer no longer waits out a 60 second poll.

03

An honest terminal state. A transaction the network no longer knows about transitions to superseded, outcome unproven, behind a bounded clock and the standing money gate. It sets no failure code, preserves its evidence, and releases the portfolio snapshot freeze that one stuck row used to inflict on everything else.

04

Repair loops that converge. The verifiers that warned every 30 seconds forever now classify their reasons (in mempool, RPC unreachable, chain echo mismatch, unreadable receipt), log once per change, back off on a schedule, and treat not yet mined as the quiet null it always should have been.

05 · Control

Stop means stop.

The deepest fix wave of the release. The Stop control was audited from the button to the database and back.

01

Visible whenever it works. The button renders off a six fact engine aggregate (active run, live lease, pending wake, pending approval, incomplete approval lifecycle, outstanding user form) pushed over IPC, so a session sleeping between timed checks shows Stop, and pressing it cancels the pending wake instead of letting the agent rise again.

02

Effective everywhere. Three engine paths that could outrun a Stop are now gated behind it under one lock discipline: approval resumes, the reconciler's own chat continuations, and launch form continuations, whose durable consumption marker (migrations 069 and 070) survives crashes, recovers orphans, and closes a deleted session's continuation exactly once. Interleavings, such as a Stop after the result lands but before the turn, or a Stop inside the lease release window, are pinned by real database tests.

03

Starts respect stops. Starting or recovering a mission with an operator Stop outstanding refuses cleanly instead of creating a run the Stop could never reach.

04

Launch outcomes by status, not by hash. A pending broadcast wakes the agent with an honest not confirmed, do not retry. Only a proven receipt says launched. The launch dialog auto dismisses only on that proof, holds on a revert, and refuses Escape or a backdrop click while a signature is in flight.

06 · Fees

The fee, stated plainly, everywhere.

01

Itemised on approval cards. Every swap and bridge approval shows VEX fee (0.25%) as its own labelled line, computed from the engine's own constants on the same amount being signed and injected through the unspoofable channel. The model structurally cannot supply or alter it. Bridge cards also gained the moved amount itself, which had never been projected.

02

The guide finally says it. How VEX works was rewritten top to bottom: 354 lines with a costs section (model tokens, gas, and the fee's three rules), the backup flow, a chains at a glance table, a UI states table, an FAQ, a glossary, and every number verified against the shipping constants. The 60 minute approval TTL replaces a wrong roughly 5 minutes, and the retired plan mode and tool names are gone from the text. The word fee appeared zero times in the old guide.

03

Treasury addresses, buyback and burn, and the charge only after success rule are unchanged from 0.2.0. Now they are simply visible.

07 · The desk

Quieter chrome, truer marks.

01

vexing. The word Working is retired. A fresh message conjures the VEX mark from a feathered radial cloud of particles in the centre of the chat, assemble, hold, disperse, with the elapsed counter beneath. Mid turn rounds show a compact vexing pill that never covers the transcript, and everything goes still while a signature awaits. The scene shows only over a provably empty viewport, latched on real transcript evidence, so it structurally cannot cover streamed content.

02

Quieter chrome. Messages slide into the transcript iOS style. Scrollbars are macOS style overlays that appear only while scrolling and sit at the panel's true edge beside the BOOK rail, and the draft field's own scrollbar got the same treatment. BOOK cards drag into any order with a soft settle animation and remember it. The session list dropped its redundant mode glyphs. Trench Photos and Launch a token merged into one Trench Express card.

03

Tool calls wear their venues again. Retiring execute_tool had silently stripped venue marks from chat. Every protocol call now canonicalizes to its venue at the main process boundary and renders its mark and a human title, and a dry run or preview can never render as an execution.

04

Icons that tell the truth. The icon layer was renamed to Lucide's own names, including the three arrows that were chevrons and the Bitcoin wallet that was a generic wallet, with zero visual change, proven by identity of the exported glyphs.

08 · Engineering

How this release was built.

The release was driven by live trading sessions: real funds on the shipping build, every break or lie filed, and every filed item closed with a named fix, an adversarial review, and a regression pinned in tests.

01

Two full multi agent cycles ran end to end before merge: six research agents with individually verified plans, seven builders with exclusive file ownership, six delta review arcs, and a three turn adversarial final review whose every finding landed as a fix with a failing test written first.

02

The suite stands at 11,474 root and 4,855 app tests, all green at the tag. The test type ratchet improved 310 baseline fingerprints, and the escape checker's blind spot for brand new test files was found and emptied.

03

Engine workers no longer race database migrations at boot, behind a startup ordering gate, and nine oversized modules were split along responsibility seams during the wave with imports left stable.

Numbers worth quoting

01

22 commits, 5 pull requests, 9 migrations (062 to 070), roughly 24k insertions net across the waves.

02

Pending lane: 5 second cadence for 10 minutes, then 30 seconds, with a durable claim lease and a token fence.

03

Approval TTL 60 minutes, now documented truthfully. Two step confirm window 4 seconds. Prepared send 10 minutes.

04

Session tool capacity: 40 injected manifests, with displacements named. Worst legal context envelope measured at 34.3% of 256k.

05

Slippage: default 100 bps, ceiling 1000 bps, rejection rather than clamping. VEX fee 25 bps. Trench curve fee 1%, which is the venue's own.

06

Invalid parameter tool calls since manifest injection: zero.

09 · Roadmap

What comes next.

01

The funded verification wave. Every fix in this release passed tests and adversarial review. The next step is the standing live probe suite: re running the original failure scenarios with real funds across all six venues, including the paths only a live chain can prove, such as a genuinely superseded launch and a live Uniswap fee leg capture.

02

Tool retention. Discovered tools currently leave a session oldest first when the 40 slot cap fills. The planned change evicts least recently used and pins anything the agent touched in its last ten turns, so a tool never vanishes mid workflow.

03

Hardened input boundaries. A root guard for all internal tool handlers, after an audit found 15 sharing a pre parse dereference pattern, is specified and awaiting the go.

04

Still on the roadmap from 0.2.0: price based Wake Up, Telegram remote control, perpetuals via Lighter, the white paper, and Windows builds. The launchpad line item is done, and it shipped as Trench Express.

10 · Before you update

Upgrade notes.

Nine migrations (062 to 070) apply automatically on first launch. Nothing is removed in 0.2.1 and no manual action is required. Two things will look different on purpose: the VEX fee now appears as a line on approval cards, where it was always charged and is now always shown, and the separate LAUNCH FEE row is gone from Activity, because the fee rides its parent operation instead.

Release 003

Release 003 · VEX 0.2.0 · Chronos

Rebuilt from the first frame.

Chronos is the largest VEX release to date. It rebuilds the first thing you see, rebuilds the thing you use most, adds the thing operators asked for most, a full history of everything the agent did, and closes an entire class of runtime failures that could silently kill a long autonomous session.

This page summarizes the work merged since 0.1.4. Versions 0.1.5 through 0.1.9 were never shipped: that work went straight into 0.2.0.

Codename Chronos · 19 migrations, applied on first launch

86

Eighty six commits over ten days: a new way in, a rebuilt transcript, a full activity ledger, and a runtime that keeps running.

A particle sigil signing itself inside the VEX brand ring

01 · First frame

A gate, not a splash screen.

VEX no longer opens on a plain splash screen. It cold opens on the Chronos Gate: a particle sigil signs itself inside the brand ring while the real launch pipeline, environment probes, Docker services, database migrations, and wizard routing, runs underneath. When the pipeline resolves, the curtain splits and you are in.

01

First install, and every version upgrade, plays a three act cinematic prologue: star field, rotating fibonacci globe, break orbit assembly onto the letterforms. After that it condenses to roughly 1.2 seconds. Any input skips it, and reduced motion users get a fully static gate.

02

Every pre shell screen (setup wizard, unlock, provider config) was rebuilt in the cobalt ink register: boxless centered composition, larger type, colour rails instead of alert boxes.

03

Settings moved into the shell. The old reconfigure wizard is gone. Settings is now a proper in app screen with calm full page sub views, and per chain private key export lives only there, behind the settings surface, never in the wizard.

02 · The transcript

The chat, rebuilt end to end.

01

The Turn Activity Island. The moment you press send, a live island mounts and moves through Working, Thinking, Calling, Writing. You watch the agent's actual reasoning stream in full, rendered as markdown and segmented per round: when a tool call lands, the current thought collapses into a stamp and the next round streams fresh underneath.

02

Reasoning is persisted. The agent's thinking and each tool's duration are stored per message and survive restarts. The transcript you reopen tomorrow shows the same reasoning it showed live.

03

No more auto scroll. The chat never yanks the view. A Latest pill offers the jump, the transcript opens at the bottom on load, and it stays exactly where you left it.

04

Honest tool cards. Tool calls render with a venue mark, a human title, and a duration, and they only claim what actually happened. Executed appears only for a proven, successful mutating operation. Quotes always carry a visible Quote label. An ambiguous result shows Pending instead of a false FAILED. Amounts render only when they match the canonical decimal exactly, or they do not render at all. Only curated venues can wear a brand mark, so a crafted tool name cannot impersonate a protocol.

05

Typography settled after live use: Instrument Serif for display, Instrument Sans at 15px on 1.65 for prose, reasoning in muted serif italic.

03 · Activity history

What exactly did my agent do with my money?

A new screen, reached from the profile menu under Radar, answers the question every self custodial agent has to answer.

01

An Etherscan like, infinitely scrolling log of every action: swaps, bridges, lends, predictions, yield operations, and fees, with filters by kind, status, protocol, chain, and session, plus day grouping, expandable rows, bridge leg audit trails, and explorer links.

02

A new accounting spine underneath it. Every broadcast is staged before signing: the intent is recorded first, the hash is taken from the signed bytes, and confirmation comes only from an on chain receipt. Ambiguity never fabricates an outcome, so a transaction the chain has not answered for stays visibly pending rather than guessed.

03

Pending transactions now resolve themselves. A 30 second background sweep asks one question per pending row: did this hash succeed or revert on its chain, by EVM receipt or Solana signature status. Success confirms, a mined revert fails, ambiguity waits. Proven end to end against a real stuck Robinhood Chain swap that older versions would have shown as pending forever.

04

A sleeping agent is no longer invisible. When the agent parks itself with a timed defer of up to 24 hours, the session shows a went to sleep banner with the wake time, a live countdown, and the agent's own stated reason. A sleeping agent never looks like a dead one again.

04 · Portfolio

The ledger book, retired.

In its place, a welcome card stack.

01

A position card with a serif display total and a unified chain row. Solana is now first class beside the EVM chains.

02

Session wallets (read only, real labels), balances with dust filtering and a full Assets view, and session activity backed by the real Agent Scan feed with a visible scope marker.

03

A Session Runtime card: the active model, the serving provider, token usage, and a context pressure meter driven by the engine's real pressure bands, so you can watch a long session approach compaction before it happens.

04

Token history: per token transaction feeds with cost basis and explorer links, one click from any exact identity token row.

05 · Reliability

The invisible half of the release.

This is the wave of fixes behind it just keeps running now. Chronos closes the known classes of silent session death.

01

Automatic context compaction, version two. Long sessions no longer stall at the context ceiling. Compaction prepares in the background from a frozen snapshot once pressure crosses 0.80, an Apply button appears when the summary is ready, and at critical pressure it applies itself. The manual compact_now tool is gone, so you never have to think about context again.

02

Provider failover. On a provider capacity failure VEX retries, then switches once per session to the highest uptime sibling endpoint, sticks to it, and re resolves pricing and context window so the meter stays honest.

03

Errors you can see. 27 SDK error types and 15 status classes now surface into a session banner, a global surface for session less failures, and a durable last error on runtime state. No more staring at a silent session wondering what happened.

04

Control that works. Approve and Reject in chat actually resume the agent. Stop is run scoped and aborts in flight inference. A stopped mission can be restarted with an operator instruction. Mission updates push instead of poll. The autonomy budget rose to 1000 iterations per turn.

05

Tool call tape integrity. A provider returning a duplicate or blank tool call id used to poison a session permanently, with every later turn rejected. The tape is now normalized in flight, deterministically, without rewriting history.

06

Memory pipeline unblocked. A chunk size mismatch had silently prevented sessions from ever receiving narrative memory. Fixed, with a bounded repair round.

07

Model catalogue and endpoints. A newest first model list, per model provider endpoint pinning ranked by uptime and restricted to tool capable endpoints, edit in place configuration that keeps your stored API key unless you type a new one, and a per model reasoning effort selector.

An honest caveat

No runtime errors is not a claim we make. What we claim is that every runtime failure class reported against 0.1.4 has a named fix in this release, the full suite is green across root, app, and end to end, and several of the fixes were proven against live incidents rather than only against tests.

06 · Venues

Deeper, and more honest.

01

Pendle, complete. 16 tools became 29: full market data (history, candles, orderbook, rewards, prices), a cross chain yields query with 20 named filters, position values with exact per leg amounts and accrued claimables, and a complete mutating surface (SY mint and redeem, dual LP add and remove, PT rollover, LP transfer, LP to PT) with per field price floors and matured market handling that either resolves correctly or refuses by name.

02

Solana, complete. The full Jupiter suite: fee bearing swaps, the borrow lifecycle, Lend Earn with a dust free full exit, and prediction markets (buy, sell, close all) with payout settlement confirmed from the keeper's own transaction. Live verified with real funds.

03

Bridges you can watch. Khalani as primary, Relay as a route bound fallback and always on for Robinhood Chain. Bridge legs are first class recorded activity with honest in flight messaging (tracked automatically, do not re bridge) and a background sweep that confirms fills from on chain evidence. Live verified in both directions with real transfers.

04

The gate audit. All 35 pre sign refusal gates were audited under one principle: gates exist to refuse theft, not market conditions. Gates that second guessed the market, such as one re validating a fresh quote against a stale one over a 0.0033% move, were removed. Gates that stop calldata exploits, overcharges, and unattributable value transfers were kept and hardened. A miscalibrated Solana priority fee cap that overstated exposure by 3.45 times was fixed. The agent trades freely inside hard safety rails, and that is the design.

05

Research tools that tell the truth. All 14 DexScreener tools were rebuilt around answering in one call: filters, sorting, paging, and self diagnosing empty results on every feed. Two tools that failed on 100% of calls in 0.1.4 were fixed, two silent row caps were exposed, and four false tool descriptions were corrected. twitter_account was restored from a total outage, and both research tools now lead every output with an untrusted content warning. The agent treats web and social content as data, never as instructions.

07 · Fees

Where the fee goes.

VEX charges a 0.25% (25 bps) integrator fee on agent executed swaps and bridges. Chronos consolidates where that fee goes and hardens how it is charged. Both treasury addresses are receive only and public:

EVM · all chains0xe341f3da256C38356bce4Afd456d7fa36E356E94
SolanaEvA1d9zMBXKFVXjSUFyHphiKUpwHJcLfZfmUH9GCd1sX
01

Aggregator swap fees (the KyberSwap route level feeReceiver, the Jupiter platform fee on the input mint) and the 25 bps bridge fee accrue to the two addresses above.

02

All collected fees fund VEX buyback and burn. The treasury addresses are public constants in the codebase, so anyone can watch them on chain.

03

Fee mechanics are safety audited. A fee is charged only after the operation it charges for succeeds, so a failure can never charge you for something that did not happen. Fee amounts and destinations are hard coded product policy that the model cannot set, raise, or redirect: a model supplied fee parameter is rejected by name, and one legacy parameter that could have routed value to an arbitrary address was found and removed in this release.

08 · Subtraction

We removed more than we added.

On purpose. Features that did not earn their place are gone, and these notes say so plainly.

01

Hyperliquid. The integration is removed wholesale, and its tables are dropped on upgrade.

02

Polymarket, Zaps (in, out, migrate), and limit orders (10 tools). Deleted.

03

FIFO and mark to market PnL, replaced by the plain, auditable agent_activity log that Agent Scan and the agent itself read. Legacy PnL projections are dropped on upgrade.

04

The subagent subsystem and its SUBAGENT_* configuration. Dead at runtime since before 0.1.0, so the config surface and the UI are gone and stale .env keys are simply ignored.

05

compact_now. Compaction is automatic now.

06

The tool output blob mechanism (tool_output_read). Tool outputs are persisted verbatim and inline, so the agent no longer reads its own results through a keyhole.

07

The reconfigure wizard, the chat auto scroll, and the NOTARY era UI chrome. The updater's Release notes button now opens projectvex.ai/releases instead of GitHub.

09 · Scale

By the numbers.

01

86 commits, roughly 385k lines touched at about 3:1 runtime to app, 19 database migrations.

02

The prompt system was rebuilt for unambiguity: roughly 290 tokens saved per turn, with invariants moved into the cached prefix.

03

Default context 256k. Compaction prepares at 0.80 pressure. Autonomy budget 1000 iterations.

04

Global slippage ceiling 1000 bps, enforced by rejection, never by silent clamping.

05

Pending transaction resolver at 30 seconds. Agent sleep up to 24 hours, now visible.

06

Pendle: 29 tools. DexScreener: 14 tools, all with full parameter vocabularies.

07

Integrator fee: 25 bps on swaps and bridges, to the treasury, funding buyback and burn.

10 · Roadmap

What comes next.

01

Price based Wake Up. Chronos made the sleeping agent visible; the next step makes it reactive. A deferred session will be able to arm a price trigger alongside its timer, so if the market moves against a position VEX wakes immediately instead of sleeping out the clock, and either acts on a pre authorized instruction or wakes with options on the table. On the way up, the same mechanism offers a stop loss, a take profit, or simply wake me and let me look. A 30 minute nap stops meaning 30 minutes of blind exposure.

02

Telegram remote control. Connect a session to Telegram and talk to VEX from anywhere: session steering, approvals, and conversation without sitting at the computer. The desktop app stays the custodian, Telegram becomes the remote.

03

An agent side token launchpad. VEX will be able to create tokens through a new launchpad integration: the agent as a launcher, not only a trader.

04

Perpetuals via Lighter. The next trading venue on the list is Lighter, a perpetuals DEX built as an application specific zk rollup on Ethereum, where the order book runs off chain but every match, funding payment, and liquidation is proven correct with zero knowledge proofs before settlement. Verifiable execution is exactly the kind of venue an autonomous agent should trade perpetuals on, and it pairs naturally with price based Wake Up.

05

The white paper. The treasury and buyback mechanics above will be specified in full there.

06

Windows. The code signing certificate is in progress. macOS (arm64 and x64, signed and notarized) and Linux ship now.

11 · Before you update

Upgrade notes.

All 19 migrations apply automatically on first launch, behind the Chronos Gate. Three are destructive by design: historical Hyperliquid rows, legacy PnL projections, and temporary tool output blobs do not survive the upgrade. Everything in the new agent_activity spine is preserved from the moment 0.2.0 first runs. If VEX was managing Hyperliquid or Polymarket positions for you, close them before you install.

Release 002

Release 002 · VEX 0.1.4

Every open community report, resolved.

VEX 0.1.4 is the community release. We triaged every open pull request and issue in the repository, all of them, back to #1: merged what was ready, rebuilt what needed hardening, and closed the board to zero.

This page summarizes the work merged since 0.1.3.

Community release · Board closed to zero

14

Fourteen merges landed: three security hardenings, a cross protocol accounting fix verified on chain, a full mission acceptance flow, and a sharper first run experience.

The VEX cobalt mark

01 · Security

Three boundaries, hardened.

VEX holds your keys, so error messages and process boundaries are safety features.

01

A correct password is never called wrong. Vault unlock now classifies failures by phase: only a failed cryptographic authentication can say "wrong password". A corrupt file says corrupt, a vault written by a newer build says update VEX, and a transient system error says try again. None of them advance the lockout throttle or steer you toward wiping keystores.

02

Helper processes lost their keyring. Docker helpers spawned by the app only need PATH and a socket. They no longer inherit your unlocked API secrets, and the strip survives Windows' case insensitive environment semantics.

03

Web research fetches only through Tavily. The raw local fetch fallback is gone: the privileged process never fetches arbitrary URLs from your machine anymore, which deletes the entire local SSRF surface instead of guarding it. Provider responses are now accounted exactly once, so duplicate, conflicting, or unrequested entries can't multiply results or poison the cache.

02 · Trade accounting

Wrapped native is native, on every chain.

A buy funded with the WETH contract address is economically the same trade as one funded with ETH. VEX's books now agree, everywhere.

01

Uniswap and KyberSwap classify by economics, not by tool name. A wrapped native leg (WETH, WBNB, WPOL, WMNT, wS, WBERA and friends) records as the native side of the trade. KyberSwap gained a fail closed wrapped native registry covering all 19 aggregator chains, with every address verified on chain before it shipped.

02

Portfolio lines can't be spoofed by a symbol. Positions aggregate by token address, never by self declared symbol, so a fake "WETH" can't melt into your real one, and brand icons render only for address verified tokens.

03

Polymarket responses are validated end to end. All nine previously raw reward and market endpoints now parse through strict, bounded schemas, so a garbled number rejects instead of silently displaying as zero.

03 · Missions

From mission ready to running: one visible path.

01

A Review & accept contract bar now appears exactly where Start mission will be. The passive header badge is no longer the only way in, and accepting closes the modal right onto the Start button. Merged directly from the community.

02

Readiness is honest. While the action plan is still loading, failed to load, or empty, every surface (badge, bar, and modal) says Preparing, and a failed read gets an explicit Retry instead of a dead end.

03

A dropped event can't hide the bar. Live sync now carries a fallback poll, so mission state stays current even if a push goes missing.

04 · First run

The composer shows what VEX can actually do.

The three starter chips are protocol forward: hunt trending memecoins through DexScreener with X sentiment, turn on Hypervexing by asking for it, scout Pendle fixed yield markets. Plan first phrasing, no fake prices, and clicking still only fills the composer. Nothing sends or trades without you.

05 · Hypervexing

Leaving the room is as smooth as entering it.

01

The exit drain animation actually plays. The trading room theme holds through the drain and hands back your own theme cleanly, with reduced motion respected.

02

Focus follows you. Into the room on enter, back to the chat composer on exit, with proper screen reader labels along the way.

03

Earn cards stopped clipping their actions in short windows.

06 · Community

This release exists because you filed it.

Every change above started as, or was shaped by, community work. Several of these changes shipped within days of the community reporting them:

01

darahub · #43, #44, #46: the vault, SSRF, and secrets findings.

02

Nishant-Adhikari · #39 merged directly, and the accounting discipline behind the registry work.

03

mandatedisrael · #37 merged directly, and #38: the mission acceptance flow.

04

alexastro01 · #36 and #40: the polish that shipped, and the best design issue this repo has received in #21.

05

ellygeronline-lab · issues #26, #41, #42: diagnoses precise enough to fix from.

Reimplemented or merged as is, every author is credited in the landing pull requests. Join the Discord and ping @lookyegbe to get into the dev channel.

07 · Engineering

Under the hood.

Update toast actions stay inside the card at every width. A corrupt Solana keystore no longer reports as a wrong password. Cache writes are best effort, so a failed local write never discards a result you already have. And VEX wears its new cobalt VX mark on every platform icon.

08 · Before you update

Upgrade notes.

No new database migrations in this release. Update and go. One behavior change worth knowing: web research now requires the free Tavily API key for fetching pages (the tool was already hidden without it), and a Tavily outage reports an honest failure instead of silently degrading. No manual action is required.

Release 001

Release 001 · VEX 0.1.3

The largest release since launch.

The headline is Hyperliquid: a full HyperCore integration with a dedicated live trading workspace called Hypervexing. Alongside it, this release closes a long list of execution honesty gaps across every DEX and bridge integration, hardens wallet approval flows, and ships several requested UX improvements from the community.

This page summarizes the work merged since 0.1.2.

Headline integration · HyperCore

31

Dedicated Hyperliquid tools across perpetuals, spot, TWAP, funding, vaults, staking, and builder fee handling.

Hyperliquid

01 · Headline integration

Hyperliquid and Hypervexing.

The centerpiece of 0.1.3 is a verified, signed integration with Hyperliquid's HyperCore, exposed to the agent as 31 dedicated tools: perpetuals with mandatory atomic stop loss, spot trading, TWAP orders, funding, vaults, staking, and builder fee handling.

When the agent enters Hyperliquid mode, the app switches into Hypervexing: a dedicated workspace with a live chart, an order book, position economics with inline stop loss and take profit editing, and a session risk panel where the operator sets leverage and notional caps that the agent's tools are gated against.

Key decisions and hardening

01

Every mutating Hyperliquid tool is live the moment the trading mode is active. An earlier release gate that hid the perp open tool behind a flag was removed after live testing showed it caused the agent to waste turns searching for a hidden tool.

02

Stop loss stays mandatory on every position open. Take profit can now be added or replaced independently through setTpsl, so a compensation flow that restores a stop after a rejected entry can no longer lose the take profit target.

03

The level 2 slippage gate was rewritten to be direction aware. It previously flagged a price improving fill as a slippage violation because it measured the absolute difference instead of the adverse direction, which caused real, false positive trade blocks in production.

04

Protection state reads now parse venue decimal values leniently instead of rejecting legitimate books, and skip validation entirely for read only tools that cannot move funds.

05

Per wallet mutation locks, durable pre sign execution intents, and complete approval previews (size, price, duration) were added ahead of the wave 2 security audit.

06

A persistent candle store lets the agent watch markets, scan for breakouts, volume spikes, moving average crosses, and RSI conditions without paying the token cost of re fetching history every turn.

07

The Hyperliquid builder fee now routes to the VEX treasury, funding VEX token buyback and burn.

02 · Cross protocol

Execution honesty across every chain and protocol.

A large share of this release is dedicated to making sure VEX never reports a trade, transfer, or approval as successful when it was not. These fixes touch nearly every execution path in the agent:

01

Transaction receipts are now checked for a reverted status everywhere the agent waits on chain. Previously a reverted approval could be treated as a granted allowance, and a reverted swap could be reported as a completed trade. This is now caught with a dedicated CONFIRMATION_UNKNOWN code so the agent never blindly retries an ambiguous outcome.

02

ERC 20 balances are checked before every approval and swap, replacing a confusing on chain revert with a clear, specific error naming the token and the shortfall.

03

Fee on transfer tokens can now be sold on Uniswap V2. The previous swap functions assumed no transfer tax and always reverted on exit for these tokens; the fee aware router variants fix that.

04

Relay, Khalani, and Polymarket integrations now report terminal failures honestly instead of quietly treating a failed or refunded bridge step, or a rejected order, as a success.

05

The trade side recorded for Uniswap and KyberSwap trades is now derived from the actual economic direction of the swap rather than the tool name that was called.

06

KyberSwap approvals are exact amount only, quotes and executions are bound to the same slippage value so a stale quote can no longer silently pass a fresh execution, and every response is verified against the expected router address before broadcast.

Several of these fixes started as community pull requests and were reimplemented on shared, cross protocol guards so the same class of bug cannot resurface in a new integration later.

03 · Operator control

Wallet, approvals, and mission safety.

01

Wallet send now flows through a proper two step approval handoff. A prepared send synthesizes the confirmation step through the standard tool path, so restricted sessions see the approval card immediately instead of requiring an extra model round trip.

02

Turns that end incomplete, whether from a timeout, an iteration limit, or exhausted context, now surface an honest, operator facing notice instead of silently looking finished.

03

Mission mode gained a hard time box. The mission duration is frozen into the run's contract the moment it starts, so nothing can move the deadline after the fact, and the turn loop stops cleanly with a dedicated deadline reached status rather than burning another inference call past the limit. A time boxed mission is now presented as time boxed, not as a failure.

04

Every mission now writes to a per wallet results ledger: a race free record of what was opened, closed, and valued, visible in a new read only Mission History panel.

05

The tool output reader gained search, path, and array query modes (where, sort, offset, limit) for large tool responses that overflow into a blob. Previously those responses could only be read as blind byte slices, which had already caused the agent to wrongly conclude a real market did not exist because the listing was cut off mid page.

04 · Runtime

Reliability and self healing.

01

The Docker based backend now recovers from a stale bind mount automatically with a non destructive recreate, instead of leaving the operator stuck at a dead end with only a support contact link.

02

Session lease handling (stop, pause, resume, retry) now follows explicit per operation contracts instead of an unobservable enqueue, so a paused or stopped session behaves predictably from the UI.

03

Mission renewal is now transactionally idempotent, and the UI hides the Renew action once a draft already exists for that slot.

05 · Activity feed

Trust and transparency in every move.

01

Token symbols shown in the Moves feed and the trading chart are now resolved only from a verified mint address. A token symbol or brand claim that arrives as free text from an activity record is always dropped rather than trusted, closing a path where a malicious or malformed token name could impersonate a known brand.

02

Explorer links were added across Moves and the tool ledger for over twenty networks, including Hyperliquid, HyperEVM, Robinhood Chain, Avalanche, Linea, Mantle, Sonic, Berachain, Ronin, Unichain, Plasma, Etherlink, Monad, MegaETH, and zkSync, so any transaction or account can be opened directly on its native block explorer.

03

The welcome screen now supports multiple configured wallets. With more than one wallet, a chip switcher shows a single wallet's holdings grouped by chain, while the combined total remains the default view.

06 · Community

Requested by the community.

Several improvements in this release were requested and, in some cases, first implemented by community members before being reviewed, hardened, and merged:

01

A searchable model picker in the provider setup wizard, replacing a paste only model id field with a live, filterable catalogue from OpenRouter.

02

Search and mode filters in the session library, so operators can find a past session by title instead of scrolling.

03

One click address copy on the wallets review card, so recovering a public address no longer requires entering edit mode.

04

The New Session dialog now defaults to Mission mode when the session list is already filtered to missions.

07 · Engineering

Under the hood.

Wave 4 of the ongoing Hyperliquid module audit split several large, mixed responsibility files into focused modules with stable public facades, including the IPC handler registry, the reconciler, and the market data normalizer. Behavior was preserved and verified with characterization tests before and after each split, so this is a maintenance investment rather than a user facing change, but it keeps the module safe to extend as Hyperliquid support grows.

08 · Before you update

Upgrade notes.

This release includes new database migrations for the Hyperliquid execution intent audit trail, the candle store, and the mission results ledger. Migrations run automatically on startup. No manual action is required.