Codex StrawberryFilter tokens checked against networks, in one pass
One sentence in, and a companion has been through the Codex filter tokens, put them where you can read them, and marked the ones it was not sure about.
Open the filter token. Check it against something else. Write the change. Move to the next one. That is the Codex afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing changed until you say so.
What it can do is exactly what Codex exposes to an account you authorise and nothing beyond it: 10 operations, 10 reads and no writes. In practice that means it can get wallet transactions, get wallet balances and get token holders, and work across the filter tokens, networks and pair stats.
The Codex API stops at Codex. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
What does it already know about your networks?
All 10 operations read.
Your account, not a guess at it: a companion can get wallet transactions, get wallet balances and get token holders, and the full list below is the whole list, with nothing inferred from Codex's documentation.
The filter tokens are what most of this inventory is about, alongside the networks. A companion can hold all 10 of these operations and forty open tabs in the same pass, which is how an afternoon of Codex admin becomes a queue you review.
- Get Wallet Transactions
- Get Wallet Balances
- Get Token Holders
- Get Token Events
- Get Token Details
- Get Token Chart
- Get Prediction Market Data
- Get Pair Stats
- Get Networks
- Filter Tokens
It can get wallet transactions. Can it act on what it finds?
Through the screens you already use.
Codex exposes no write operation to a connected account, so a companion drives Codex in the session you are already signed into instead, filling the same forms you would to move a filter token, and anything consequential stops for an approval card before it happens.
That is the ordinary case rather than the exception. Most of what a filter token in Codex touches has no API pointed at it, and a companion is useful precisely because it does not need one.
Does the filter token sweep have to be asked for every time?
Yes.
Saved as a routine, the Codex filter tokens pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the engineering admin, the Codex filter tokens sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents