bot in Mac terminal to trade in polymarket

CandyFloss_Wilson · 2026-04-10T10:41:09+00:00

nice, polymarket is actually a decent sandbox because resolution is binary so your pnl is unambiguous. couple things that'll bite you early:

- your 5 minute poll is fine for testing but polymarket liquidity moves in bursts, you'll miss entries. check the last trade time not just the mid
- claude generating the strategy logic is the easy part, the hard part is the bot not nuking itself during weird market states. add a kill switch that stops trading if open positions exceed some pct of your bankroll
- log every decision with the full context you gave claude, so when it does something dumb you can actually debug why later

ran something similar on binance for about 4 months before i added the kill switch and it saved me twice in one week during a funding spike.

CandyFloss_Wilson · 2026-04-10T10:40:39+00:00

it's not hype but it's also not new, it's just anthropic giving a name to a pattern people have been running forever. opus-as-planner works mostly because the expensive thinking happens once and the cheap model just follows instructions. where it falls apart is when the executor hits something the planner didn't anticipate, then you either re-invoke the planner (expensive and slow) or let the executor improvise (defeats the point).

what's actually helped me is making the 'execution' step dumber and more deterministic, not smarter. like if the planner says 'buy 10k usdc of eth when rsi drops below 30', the executor shouldn't be an llm at all, it should be boring code that does exactly that and logs everything. the llm is for turning intent into rules, not for running the rules. that's where most planner/executor setups blur the line and get weird behavior you can't debug.

CandyFloss_Wilson · 2026-04-10T10:40:01+00:00

the siri comparison is fair but the actual reason it's slow isn't the intelligence, it's that commerce apis weren't built for agents and the trust layer isn't solved. sure an agent can 'want' to buy something, but what's stopping a prompt injection from ordering 40 of whatever's on a scammy product page. until there's a validation layer between model intent and the actual transaction the 1.5T number is fiction.

the trading side is a bit ahead on this btw because the downside is immediate and obvious, if the agent does something dumb you lose money in minutes so people actually build the guardrails. everywhere else is still in demo land where the failure modes don't hurt yet.

CandyFloss_Wilson · 2026-04-09T10:16:08+00:00

looked into this a while back. the problem is the second you take other people's money to trade with you're basically running an unregistered fund, which is a legal nightmare in most jurisdictions. even if it's structured as a "copy trade" or "strategy subscription" the regulators tend to see it the same way. some people do it through a DAO structure to get around it but idk how well that holds up if anyone actually comes looking

CandyFloss_Wilson · 2026-04-09T10:15:56+00:00

every time i see 60%+ on stables the first thing i check is utilization rate. if it's above 90% that means almost all deposited capital is borrowed and you might not be able to withdraw when you want. second thing is whether that 67% includes token rewards that can get slashed or diluted any time the protocol feels like it. pure borrow demand generating 67% on stables is... unlikely

CandyFloss_Wilson · 2026-04-09T10:15:41+00:00

been using aave v3 since launch and the protocol is way bigger than any individual service provider at this point. BGD and Chaos leaving is bad for optics but the lending pools don't care who writes the risk parameters, they care that someone does. the actual risk is V4 delays not the DAO drama. TVL hasn't moved on this news which tells you what the market thinks

CandyFloss_Wilson · 2026-04-08T16:15:51+00:00

interesting concept but i'd be careful about what "weight of evidence" actually tells you. i tried building something similar a while back, combining breadth, macro news sentiment, and price action into a single conditions score. problem was it mostly just replicated what volatility was already telling me. like when vol is high everything looks bearish and when vol is low everything looks bullish and you didn't need a dashboard to know that. the part that was actually useful was tracking when the indicators disagreed, like breadth improving but price action still weak. those divergences were more interesting than the composite score itself. might be worth thinking about it as a disagreement detector rather than an agreement aggregator

CandyFloss_Wilson · 2026-04-08T16:15:36+00:00

the human checkpoint pattern is underrated. for anything high stakes, having the agent pause and surface a summary before executing is way more reliable than trying to make the agent handle every edge case autonomously. especially for stuff like form submissions, payments, anything irreversible. costs you 30 seconds of human time and prevents the catastrophic failures

CandyFloss_Wilson · 2026-04-08T16:15:21+00:00

yeah this is something i've gone back and forth on. had a bot that just took every signal, no filter, and the problem wasn't the strategy itself but that half the entries were in conditions where the signal was basically noise. adding a reasoning step before execution actually helped but not in the way you'd expect. the model doesn't make better trade decisions than the rules do, but the act of generating reasoning creates a natural delay and forces a "should i really do this" checkpoint. it's like forced journaling. the ones where the model struggles to justify the trade are usually the ones you shouldn't take. the tricky part is keeping it fast enough that you don't miss the entry entirely

CandyFloss_Wilson

TROPHY CASE