Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

I built a custom TradingView indicator with Claude Code & Fable 5. It's called the Storm Gauge and is built off a real quant trading strategy. I open-sourced the full code on GitHub. Free to install, free to fork, yours to improve. Here's how to install a quant indicator... on your TradingView chart: What it actually is The Storm Gauge is a live implementation of the GARCH model, a Nobel Prize-winning volatility framework that real quant desks run daily. It forecasts how "violent" tomorrow's market could be by combining three inputs: an asset's baseline volatility, yesterday's shock, and where volatility was already sitting before that shock happened. It doesn't predict market direction. Instead, it measures risk, in real time, on your actual chart. How to install it Method 1. Plugin command Open the GitHub repo: Find the installation section, copy the command, and paste it into Claude Code. It runs the plugin install automatically. Method 2. Manual config Open garchmethod.md in the repo, copy the entire file, and paste it into Claude Code. It fetches the skill files directly and verifies the strategy for you. (you only need one method; I'm just showing both) Getting it onto your TradingView chart Inside the repo, there's a Pine Script folder. Open it, copy the entire file. Go into TradingView's Pine Editor, paste it in, hit Enter, and refresh. That's it. The Storm Gauge now runs live on your chart as a real number. Once it's installed, just talk to it: → "What's the volatility forecast on Bitcoin?" → "Explain what the current volatility forecast means on $BTC and how it should impact my position sizing" → "Help me size my S&P500 position according to current market volatility" Does it actually work? I backtested the same EMA cross strategy two ways across 15 years of BTC data. Same entries, same exits. → Fixed position sizing: $17,957 final equity → Storm Gauge (GARCH) sizing: $21,205 final equity Fewer drawdowns, less risk, better result. Full breakdown of the entire build process in my recent article - pinned on my profile.show more

Miles Deutscher

677,891 subscribers

56,625 Aufrufe • vor 3 Monaten •via X (Twitter)

Wissenschaft & Technologie Finanzen

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

I used Claude Code to build and automate a legitimate quant trading strategy. The framework I built is based on the GARCH model, and it's one of the most-used trading models by real quant desks. The crazy thing is, I just completely open-sourced the GitHub repo. It contains: a Pine Script indicator for TradingView that loads the quant strategy in real time, complete installation instructions, a reusable Claude Skill & more. This is probably the most-valuable thing I've shared on 𝕏 in 2026. →

I used Claude Code to build and automate a legitimate quant trading strategy. The framework I built is based on the GARCH model, and it's one of the most-used trading models by real quant desks. The crazy thing is, I just completely open-sourced the GitHub repo. It contains: a Pine Script indicator for TradingView that loads the quant strategy in real time, complete installation instructions, a reusable Claude Skill & more. This is probably the most-valuable thing I've shared on 𝕏 in 2026. →

Miles Deutscher

88,351 Aufrufe • vor 3 Monaten

Claude can reverse engineer any trading bot on GitHub and explain exactly how the strategy works. Point it at any repo. It reads the code and rebuilds the logic from scratch. Every quant strategy on the internet just became readable.

Claude can reverse engineer any trading bot on GitHub and explain exactly how the strategy works. Point it at any repo. It reads the code and rebuilds the logic from scratch. Every quant strategy on the internet just became readable.

0xMarioNawfal

82,084 Aufrufe • vor 7 Monaten

It is becoming f*cking dangerous: the NSA's own reverse-engineering tool now plugs straight into Claude Code - Ghidra has 94k stars, and GhidraMCP lets your agent read a compiled program instead of guessing what it does Install Ghidra 12.1.4 from ghidra-sre,org (free, released by the NSA) Download the GhidraMCP release and add it in File -> Install Extensions Restart Ghidra and switch on GhidraMCPPlugin in File -> Configure -> Developer Connect it: claude mcp add ghidra -- uvx --from git+ ghidra-mcp Open a binary you're allowed to analyze and let Ghidra run its analysis Ask Claude what a function does: it decompiles it, renames the variables and explains it in plain English Ask for the map: every function, import, string and cross-reference, and where the interesting code lives The decompiling runs in Ghidra on your machine, Claude just drives it Malware samples, old firmware, your own builds: your agent reads the program itself, not the docs about it Find the repo in the reply below

It is becoming f*cking dangerous: the NSA's own reverse-engineering tool now plugs straight into Claude Code - Ghidra has 94k stars, and GhidraMCP lets your agent read a compiled program instead of guessing what it does Install Ghidra 12.1.4 from ghidra-sre,org (free, released by the NSA) Download the GhidraMCP release and add it in File -> Install Extensions Restart Ghidra and switch on GhidraMCPPlugin in File -> Configure -> Developer Connect it: claude mcp add ghidra -- uvx --from git+ ghidra-mcp Open a binary you're allowed to analyze and let Ghidra run its analysis Ask Claude what a function does: it decompiles it, renames the variables and explains it in plain English Ask for the map: every function, import, string and cross-reference, and where the interesting code lives The decompiling runs in Ghidra on your machine, Claude just drives it Malware samples, old firmware, your own builds: your agent reads the program itself, not the docs about it Find the repo in the reply below

Archive

16,420 Aufrufe • vor 21 Tagen

THESE 2 FREE REPOS SHOULD HONESTLY BE ILLEGAL. ONE SENTENCE TO CLAUDE CODE, 60 SECONDS OF WATCHING, AND A DESKTOP TRADING CHART IS RUNNING ON 4 EXCHANGES IN YOUR TERMINAL FOR $0. they're called rea and ccxt. both open source. here's how it works: > rea reads 18,402 trades and finds how the app builds its footprint chart > it rebuilds it in 256 lines, 12 of 12 tests passed > ccxt feeds it binance, okx, bybit and coinbase at once here's how to run it: 1 → pip install ccxt 2 → plug rea into claude code 3 → ask it to rebuild one chart in your terminal honestly the spread line is the part i keep watching: buy coinbase, sell bybit, 11.3 bps. how the replay ends is on screen in the clip. i won't say anything more. bookmark this ↓

THESE 2 FREE REPOS SHOULD HONESTLY BE ILLEGAL. ONE SENTENCE TO CLAUDE CODE, 60 SECONDS OF WATCHING, AND A DESKTOP TRADING CHART IS RUNNING ON 4 EXCHANGES IN YOUR TERMINAL FOR $0. they're called rea and ccxt. both open source. here's how it works: > rea reads 18,402 trades and finds how the app builds its footprint chart > it rebuilds it in 256 lines, 12 of 12 tests passed > ccxt feeds it binance, okx, bybit and coinbase at once here's how to run it: 1 → pip install ccxt 2 → plug rea into claude code 3 → ask it to rebuild one chart in your terminal honestly the spread line is the part i keep watching: buy coinbase, sell bybit, 11.3 bps. how the replay ends is on screen in the clip. i won't say anything more. bookmark this ↓

RetroChainer

12,061 Aufrufe • vor 21 Tagen

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

You can now use Jev right inside Claude Code 🤯 It's called jev-model-router, an early access mod built on Claude Code's new function hooks. Before every turn, it checks in with Jev and asks: > how mechanical the task is > how much reasoning it needs > whether it's risky Then it routes: → it'll move up to a stronger model on weak evidence, and only drops to a cheaper one when it's confident the task is simple → every decision gets logged in your transcript → if the call fails, your request runs untouched Setup: 1. copy the install command: npx claude-code-templates@latest --mod productivity/jev-model-router 2. paste it inside Claude Code 3. run claude with CLAUDE_CODE_ENABLE_FUNCTION_HOOKS=1 set 4. accept the trust prompt on first launch Link: Also works with no api key, it just falls back to a built-in classifier with no confidence score. For real jev routing, add your typesafeApiKey or gatewayApiKey to ~/.claude/settings.json. Follow me for more AI workflows and tutorials.

Alvaro Cintas

44,575 Aufrufe • vor 1 Monat

Claude Code upgraded my grandma’s old TV to a real Smart TV with one prompt... For years she couldn’t watch anything on it. Netflix wouldn’t open. YouTube kept saying “update required”. The TV was stuck on software from 2018 and the company stopped caring about it a long time ago So I typed one line into Claude Code: flash my Android TV to the new Smart TV firmware Here’s what it did, in simple words: → It found the TV on her Wi-Fi and connected to it → It checked the model and the old system. Android 9 → It put the TV into update mode and installed a brand new system. 6.4 GB in about 41 seconds → It checked every part of the install, then restarted the TV The TV came back on with a new system, 4K HDR and a voice assistant. Then Claude installed YouTube, Netflix, Prime Video, Spotify, Disney+ and the Play Store by itself Same TV. Same remote. Zero dollars She thinks I bought her a new one Want to try it on an old TV at home: step 1 → open Claude Code and paste the prompt from the first comment step 2 → it checks your exact model and finds the official update for it step 3 → it tells you what it’s going to do before it touches anything What old device should I bring back to life next?

Rikitan

50,914 Aufrufe • vor 20 Tagen

Give Opus 5.5 𝗮 𝗰𝗹𝗶𝗰𝗸𝗮𝗯𝗹𝗲 𝗺𝗼𝘁𝗶𝗼𝗻 𝗱𝗶𝗰𝘁𝗶𝗼𝗻𝗮𝗿𝘆: 𝟭𝟮𝟬 𝗺𝗼𝘃𝗶𝗻𝗴 𝘀𝗮𝗺𝗽𝗹𝗲𝘀, each labelled with its name and a ready-made prompt. Click the ones you like, and Claude Code builds them into your video or site. Five packs: motion graphics, camera moves and transitions, UI components, landing page and web effects, and photo looks and lighting. Four steps: 1. Paste the line at the end into Claude Code to install the skill 2. Tell it "Open the motion-prompt library" 3. Tick the samples you like in the gallery and press "Send to AI" 4. Back in Claude Code, say "Edit the opening of this video like this" It gets each sample's motion spec and reference code, and it works with Remotion, CSS or Canvas. Without the skill, press "Copy picks" and paste them in. Paste this into Claude Code and it installs itself 👇 "Read and install the motion-prompt skill in this environment. When it is installed, tell me how to use it in three lines."

Give Opus 5.5 𝗮 𝗰𝗹𝗶𝗰𝗸𝗮𝗯𝗹𝗲 𝗺𝗼𝘁𝗶𝗼𝗻 𝗱𝗶𝗰𝘁𝗶𝗼𝗻𝗮𝗿𝘆: 𝟭𝟮𝟬 𝗺𝗼𝘃𝗶𝗻𝗴 𝘀𝗮𝗺𝗽𝗹𝗲𝘀, each labelled with its name and a ready-made prompt. Click the ones you like, and Claude Code builds them into your video or site. Five packs: motion graphics, camera moves and transitions, UI components, landing page and web effects, and photo looks and lighting. Four steps: 1. Paste the line at the end into Claude Code to install the skill 2. Tell it "Open the motion-prompt library" 3. Tick the samples you like in the gallery and press "Send to AI" 4. Back in Claude Code, say "Edit the opening of this video like this" It gets each sample's motion spec and reference code, and it works with Remotion, CSS or Canvas. Without the skill, press "Copy picks" and paste them in. Paste this into Claude Code and it installs itself 👇 "Read and install the motion-prompt skill in this environment. When it is installed, tell me how to use it in three lines."

Vox

65,087 Aufrufe • vor 28 Tagen

if you use claude code, this will save you real money. the problem: every time you make an edit, your ai rereads the whole codebase to figure out what changed. tens of thousands of tokens, every turn, for context it already had. this repo fixes it. it’s called code review graph, and it just maps your entire codebase: every file, every function, every connection laid out so you can see the actual shape of your project how to set up (2 min): 1. pip install code-review-graph 2. code-review-graph install - auto-configures Claude Code, Cursor, Codex, Gemini CLI + more 3. code-review-graph build change one function, and it traces exactly what that touches... every caller, every dependent file, every test. your ai only reads what's affected, not the whole repo. and the savings are wild. a task that used to burn ~100,000 tokens (about a dollar) now runs closer to a penny.

if you use claude code, this will save you real money. the problem: every time you make an edit, your ai rereads the whole codebase to figure out what changed. tens of thousands of tokens, every turn, for context it already had. this repo fixes it. it’s called code review graph, and it just maps your entire codebase: every file, every function, every connection laid out so you can see the actual shape of your project how to set up (2 min): 1. pip install code-review-graph 2. code-review-graph install - auto-configures Claude Code, Cursor, Codex, Gemini CLI + more 3. code-review-graph build change one function, and it traces exactly what that touches... every caller, every dependent file, every test. your ai only reads what's affected, not the whole repo. and the savings are wild. a task that used to burn ~100,000 tokens (about a dollar) now runs closer to a penny.

Alvaro Cintas

75,596 Aufrufe • vor 3 Monaten

Chinese Microsoft Quants built their own trading research AI quant that replaces them - dropped 15k star repo the twist: in backtests it made ~2x more per year than the formulas Quants have used for years here's how thier AI Quant works, step by step: step 1 → it writes trading hypothesis like a quant would - e.g. "volume-confirmed reversal beats momentum in high-vol markets" step 2 → it turns idea into factor code and backtests it in Qlib on CSI 300 and NASDAQ-100 data step 3 → it reads the result, keeps what works, kills what doesn't and tunes factors and models together in a loop how to steal this for your own trading system: step 4 → hand the repo to Claude Code - "pip install rdagent", add your LLM key, "rdagent health_check", then "rdagent fin_quant" step 5 → set Opus 5.5 in the .env to the newest model you have - it runs on LiteLLM, so Claude, GPT or Gemini all plug in step 6 → drop your research into "rdagent fin_factor_report" - it turns financial reports into factors it can backtest step 7 → open "rdagent server_ui" - watch every hypothesis, line of code and backtest live, then copy the winning factors into your own system the result: 14.21% vs 5.70% annual return on CSI 300 and an information ratio of 1.77 on NASDAQ-100 in backtests - with 70% fewer-factors, for under $10 accepted at NeurIPS 2025 Run it today, not tomorrow. Then read article below on your own 24/7 AI trading system:

Chinese Microsoft Quants built their own trading research AI quant that replaces them - dropped 15k star repo the twist: in backtests it made ~2x more per year than the formulas Quants have used for years here's how thier AI Quant works, step by step: step 1 → it writes trading hypothesis like a quant would - e.g. "volume-confirmed reversal beats momentum in high-vol markets" step 2 → it turns idea into factor code and backtests it in Qlib on CSI 300 and NASDAQ-100 data step 3 → it reads the result, keeps what works, kills what doesn't and tunes factors and models together in a loop how to steal this for your own trading system: step 4 → hand the repo to Claude Code - "pip install rdagent", add your LLM key, "rdagent health_check", then "rdagent fin_quant" step 5 → set Opus 5.5 in the .env to the newest model you have - it runs on LiteLLM, so Claude, GPT or Gemini all plug in step 6 → drop your research into "rdagent fin_factor_report" - it turns financial reports into factors it can backtest step 7 → open "rdagent server_ui" - watch every hypothesis, line of code and backtest live, then copy the winning factors into your own system the result: 14.21% vs 5.70% annual return on CSI 300 and an information ratio of 1.77 on NASDAQ-100 in backtests - with 70% fewer-factors, for under $10 accepted at NeurIPS 2025 Run it today, not tomorrow. Then read article below on your own 24/7 AI trading system:

bodila

12,948 Aufrufe • vor 19 Tagen

Claude Mobile starts the idea... Ghostty finishes it I basically use Claude Mobile as a notepad now. Whenever something comes to mind, I open the app, pick a repo, and ask Claude to start exploring. Then I just let it run while I go on with my day. Later I jump into Claude Desktop and I’m right back in the same session, with context, structure, and a clearer shape of the idea. I tweak a few things to set up the coding phase. Finally, one click to Ghostty (video), open a couple of worktrees, and start working on the PR. IMPORTANT: when you move to Ghostty, it must be the exact same repo you started on mobile, otherwise the --teleport command will fail

Claude Mobile starts the idea... Ghostty finishes it I basically use Claude Mobile as a notepad now. Whenever something comes to mind, I open the app, pick a repo, and ask Claude to start exploring. Then I just let it run while I go on with my day. Later I jump into Claude Desktop and I’m right back in the same session, with context, structure, and a clearer shape of the idea. I tweak a few things to set up the coding phase. Finally, one click to Ghostty (video), open a couple of worktrees, and start working on the PR. IMPORTANT: when you move to Ghostty, it must be the exact same repo you started on mobile, otherwise the --teleport command will fail

Daniel San

67,891 Aufrufe • vor 9 Monaten

I still don't understand why everyone is not using this yet. Thanks to it, a year ago I increased my income to 17,000 dollars a month Andrey Karpathy, co-founder of OpenAI, published a simple idea that got 16 million views: stop using AI to write code, use it to build a second brain You point Claude Code to a folder, drop any source in there (an article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. It compounds like interest: the more you feed it, the smarter it gets Here is the gist: Install Obsidian, create a vault, open it in Claude Code Paste the file with Karpathy's wiki idea and tell Claude to build it Claude creates three folders: raw for sources, wiki for its pages, CLAUDE which runs everything Drop any source into raw and say "ingest this" Ask questions across everything, forever Five minutes to set up, and you never start with an empty chat again The full step-by-step guide is in the article. Save to bookmarks

I still don't understand why everyone is not using this yet. Thanks to it, a year ago I increased my income to 17,000 dollars a month Andrey Karpathy, co-founder of OpenAI, published a simple idea that got 16 million views: stop using AI to write code, use it to build a second brain You point Claude Code to a folder, drop any source in there (an article, transcript, PDF) and Claude reads it, links it, and saves it into a living wiki of everything you know. It compounds like interest: the more you feed it, the smarter it gets Here is the gist: Install Obsidian, create a vault, open it in Claude Code Paste the file with Karpathy's wiki idea and tell Claude to build it Claude creates three folders: raw for sources, wiki for its pages, CLAUDE which runs everything Drop any source into raw and say "ingest this" Ask questions across everything, forever Five minutes to set up, and you never start with an empty chat again The full step-by-step guide is in the article. Save to bookmarks

Bober_smart

2,889,317 Aufrufe • vor 2 Monaten

How to build a viral Web3 app in an afternoon using the ChainGPT AI skill for Claude Code. No coding experience required. I built Roast My Wallet. Paste any Ethereum wallet address, get a savage AI-generated roast of your trading history, a Degen Score out of 100, an on-chain report card, and three AI-generated NFT portraits. Here's exactly how it came together. Setup (3 minutes): 🔸Install Claude Code at 🔸Run /plugin install ChainGPT-org/chaingpt-claude-skill 🔸Get an API key at 🔸Type /chaingpt and describe what you want to build What the skill actually does: The ChainGPT skill doesn't just give you starter code. It knows the entire API. Every endpoint, every parameter, every credit cost, every error code. When I asked it to build the roast feature, it knew to call the LLM endpoint, how to stream the response back to the browser in real time, and how to handle errors automatically. I didn't look up a single thing. How it works under the hood: 1. Pulls real ETH balance and transaction count from the Ethereum blockchain 2. Feeds those numbers into ChainGPT's LLM and streams the roast back live 3. Calculates a Degen Score from your tx count vs balance ratio 4. Generates a report card with letter grades across Trading, Patience, Risk, Diamond Hands, and NGMI 5. Uses the roast text to generate three custom NFT portraits in parallel via VeloGen 6. Packages everything into a downloadable PNG card ready to post 7. Every feature came from describing what I wanted: 8. "Make the API key server-side." Done. 9. "Add an animated arc gauge for the degen score." Done. 10. "Generate NFT portraits using the roast text as context." Done. I never wrote a function or debugged an API response. I described outcomes. The ChainGPT skill handled the rest. If you can describe what you want to build, you can build it. Get your API key. Install the skill. /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build with ChainGPT AI!

How to build a viral Web3 app in an afternoon using the ChainGPT AI skill for Claude Code. No coding experience required. I built Roast My Wallet. Paste any Ethereum wallet address, get a savage AI-generated roast of your trading history, a Degen Score out of 100, an on-chain report card, and three AI-generated NFT portraits. Here's exactly how it came together. Setup (3 minutes): 🔸Install Claude Code at 🔸Run /plugin install ChainGPT-org/chaingpt-claude-skill 🔸Get an API key at 🔸Type /chaingpt and describe what you want to build What the skill actually does: The ChainGPT skill doesn't just give you starter code. It knows the entire API. Every endpoint, every parameter, every credit cost, every error code. When I asked it to build the roast feature, it knew to call the LLM endpoint, how to stream the response back to the browser in real time, and how to handle errors automatically. I didn't look up a single thing. How it works under the hood: 1. Pulls real ETH balance and transaction count from the Ethereum blockchain 2. Feeds those numbers into ChainGPT's LLM and streams the roast back live 3. Calculates a Degen Score from your tx count vs balance ratio 4. Generates a report card with letter grades across Trading, Patience, Risk, Diamond Hands, and NGMI 5. Uses the roast text to generate three custom NFT portraits in parallel via VeloGen 6. Packages everything into a downloadable PNG card ready to post 7. Every feature came from describing what I wanted: 8. "Make the API key server-side." Done. 9. "Add an animated arc gauge for the degen score." Done. 10. "Generate NFT portraits using the roast text as context." Done. I never wrote a function or debugged an API response. I described outcomes. The ChainGPT skill handled the rest. If you can describe what you want to build, you can build it. Get your API key. Install the skill. /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build with ChainGPT AI!

ChainGPT

29,339 Aufrufe • vor 6 Monaten

Claude Code can now go find the right skill itself, instead of you searching for one. it's called find-skills. a small package that plugs into Claude Code, and instead of you hunting for rest, you just describe the task and it searches the whole open skills ecosystem, finds the ones that fit, and installs them for you. > tell it what you're trying to do, in plain english > it scans the skills registry and maps your task to real skills > it pulls the right ones in and sets them up half the time you don't even know a skill exists for what you're doing. now you don't have to.

Claude Code can now go find the right skill itself, instead of you searching for one. it's called find-skills. a small package that plugs into Claude Code, and instead of you hunting for rest, you just describe the task and it searches the whole open skills ecosystem, finds the ones that fit, and installs them for you. > tell it what you're trying to do, in plain english > it scans the skills registry and maps your task to real skills > it pulls the right ones in and sets them up half the time you don't even know a skill exists for what you're doing. now you don't have to.

Alvaro Cintas

38,829 Aufrufe • vor 3 Monaten

save these two free services. they are what i built my Polymarket strategies on, the ones paying me around $10,000 a month. what it looks like day to day: you ask any question about the market in plain words, Claude Code digs through the data and comes back with numbers. you become a quant researcher. 1 - poly_data one command and every Polymarket trade sits on your own disk. who bought, when, at what price, what size, and who was standing on the other side of it. my first sync pulled 3.1 million markets. you can pull apart the edge of any trader on Polymarket you like. first sync runs a few hours, leave it overnight, after that updates land in seconds. 2 - pendulumflow archive this one holds the book itself: what orders were sitting there, at what prices, what size, second by second, on every single market. 288 billion events recorded, and 2.3 billion more coming in every day. i used to pay $200 a month for this kind of data. here you just open it and take it, nothing to sign up for. the front page has ready made questions you copy straight into Claude Code. the project runs on donations, storing and serving this much data costs real money every month. so if you start using it, send the guy something, he is carrying all of it alone. these two will give you what only a handful of people on this market have.

save these two free services. they are what i built my Polymarket strategies on, the ones paying me around $10,000 a month. what it looks like day to day: you ask any question about the market in plain words, Claude Code digs through the data and comes back with numbers. you become a quant researcher. 1 - poly_data one command and every Polymarket trade sits on your own disk. who bought, when, at what price, what size, and who was standing on the other side of it. my first sync pulled 3.1 million markets. you can pull apart the edge of any trader on Polymarket you like. first sync runs a few hours, leave it overnight, after that updates land in seconds. 2 - pendulumflow archive this one holds the book itself: what orders were sitting there, at what prices, what size, second by second, on every single market. 288 billion events recorded, and 2.3 billion more coming in every day. i used to pay $200 a month for this kind of data. here you just open it and take it, nothing to sign up for. the front page has ready made questions you copy straight into Claude Code. the project runs on donations, storing and serving this much data costs real money every month. so if you start using it, send the guy something, he is carrying all of it alone. these two will give you what only a handful of people on this market have.

may.crypto {🦅}

26,523 Aufrufe • vor 2 Monaten

I built an AI trading bot with Jev + Opus 5.5, and it's probably too powerful for public use, but f*ck it... It's a high-frequency algo trading framework that prints. Open the article, copy/paste it into Claude Code. You're welcome.

I built an AI trading bot with Jev + Opus 5.5, and it's probably too powerful for public use, but f*ck it... It's a high-frequency algo trading framework that prints. Open the article, copy/paste it into Claude Code. You're welcome.

Miles Deutscher

199,310 Aufrufe • vor 1 Monat

I OPEN-SOURCED MY CRYPTO TRADING BOT ON GITHUB. 100% FREE It's called Cabbage. A spot trading bot you can backtest, paper-trade and run live, one command each. Full step-by-step setup guide. It runs on two models: > Astra (GPT-6) built it. Smart but slow. It thinks, writes the code, explains every decision. > Jev runs it. Jev doesn't talk. One word and a probability, in milliseconds. BUY, HOLD or SELL. Under 0.80 it waits. Here's what's inside: 1. Signal engine RSI 14 + EMA 12/26 confluence. It only reads closed candles, so no fake signals from a candle that's still moving. 2. Hard risk rules Fixed ticket size and a percentage stop-loss on every entry. The bot can't size up because it "feels confident". 3. Backtest → HTML report Event-driven backtest that replays history candle by candle, like it's trading live. You get a full HTML report at the end. 4. Paper trading Real exchange data, local fills, zero money at risk. Run one iteration to test, then leave it running. 5. Live trading Real orders on any exchange CCXT supports. Your keys stay in your own .env file. 6. Doctor command Checks your config and exchange connection before you trade. No orders placed. State is saved in SQLite per market and pair, so a restart doesn't wipe your positions. Built on Investing Algorithm Framework 9. Apache-2.0, fork it and make it yours.

I OPEN-SOURCED MY CRYPTO TRADING BOT ON GITHUB. 100% FREE It's called Cabbage. A spot trading bot you can backtest, paper-trade and run live, one command each. Full step-by-step setup guide. It runs on two models: > Astra (GPT-6) built it. Smart but slow. It thinks, writes the code, explains every decision. > Jev runs it. Jev doesn't talk. One word and a probability, in milliseconds. BUY, HOLD or SELL. Under 0.80 it waits. Here's what's inside: 1. Signal engine RSI 14 + EMA 12/26 confluence. It only reads closed candles, so no fake signals from a candle that's still moving. 2. Hard risk rules Fixed ticket size and a percentage stop-loss on every entry. The bot can't size up because it "feels confident". 3. Backtest → HTML report Event-driven backtest that replays history candle by candle, like it's trading live. You get a full HTML report at the end. 4. Paper trading Real exchange data, local fills, zero money at risk. Run one iteration to test, then leave it running. 5. Live trading Real orders on any exchange CCXT supports. Your keys stay in your own .env file. 6. Doctor command Checks your config and exchange connection before you trade. No orders placed. State is saved in SQLite per market and pair, so a restart doesn't wipe your positions. Built on Investing Algorithm Framework 9. Apache-2.0, fork it and make it yours.

sopersone

62,070 Aufrufe • vor 1 Monat

Quant can now see and control your charts. Symbols, timeframes, chart types, layouts, sessions, visible ranges. Ask, and it changes them. It also sees what it built. Indicators and strategies from Quant, or any Pine Script® code, get fixed and improved visually, right on the chart. Live now.

Quant can now see and control your charts. Symbols, timeframes, chart types, layouts, sessions, visible ranges. Ask, and it changes them. It also sees what it built. Indicators and strategies from Quant, or any Pine Script® code, get fixed and improved visually, right on the chart. Live now.

LuxAlgo

11,836 Aufrufe • vor 1 Monat

I have a little robot that unlocks my door from the inside (so I don't have to carry a key) The problem was it wouldn't calibrate on my door. It was designed for 90° turns, but my lock only needs 15° In the past, this would've been a showstopper But I asked AI if it could help... At first, it suggested I snoop on the bluetooth connection to figure out the protocol Then it realized that we could probably just decompile the app's SDK and read its source code. That worked! It told me to switch to my mac and run some python for it. Unfortunately, it couldn't run the scripts directly because Claude Code Desktop didn't have bluetooth permissions, but my shell did. Thinking about it now, I probably should've used Claude Code or Codex in the Terminal. Anyways, it took a while, lots of backs and forths, we had some misunderstandings, it was massively overcautious in the beginning, but we finally got the lock calibrated! Feels like magic! I threw the repo up on github in case anyone in the future (ie me) runs into a similar issue – hopefully it can save them some time

I have a little robot that unlocks my door from the inside (so I don't have to carry a key) The problem was it wouldn't calibrate on my door. It was designed for 90° turns, but my lock only needs 15° In the past, this would've been a showstopper But I asked AI if it could help... At first, it suggested I snoop on the bluetooth connection to figure out the protocol Then it realized that we could probably just decompile the app's SDK and read its source code. That worked! It told me to switch to my mac and run some python for it. Unfortunately, it couldn't run the scripts directly because Claude Code Desktop didn't have bluetooth permissions, but my shell did. Thinking about it now, I probably should've used Claude Code or Codex in the Terminal. Anyways, it took a while, lots of backs and forths, we had some misunderstandings, it was massively overcautious in the beginning, but we finally got the lock calibrated! Feels like magic! I threw the repo up on github in case anyone in the future (ie me) runs into a similar issue – hopefully it can save them some time

Steve Krouse

38,720 Aufrufe • vor 3 Monaten

My Claude bot finished first night profit $2,314 I built the script in 4 hours and it was worth it Average winrate 70% This is not clickbait it is a story about a 5 minute BTC script My strategy + Claude = all you need Wallet: Copytrade: Here is the full strategy: 5 Minute BTC and ETH Micro Arbitrage The system trades short 5 minute Bitcoin and Ethereum contracts In fast markets temporary mispricings appear when YES + NO drops below one dollar The bot scans in real time and captures the spread the moment it appears Speed over emotion When volatility spikes and manual traders hesitate the system reacts automatically Orders execute instantly without delay hesitation or emotional bias By the time most traders understand what happened the opportunity window is already gone Automation compounds the edge Instead of chasing large wins the strategy captures small spreads repeatedly High frequency execution allows the bot to run continuously stacking micro advantages into meaningful returns over time All that is left is refining the code deploying at scale and letting it run

My Claude bot finished first night profit $2,314 I built the script in 4 hours and it was worth it Average winrate 70% This is not clickbait it is a story about a 5 minute BTC script My strategy + Claude = all you need Wallet: Copytrade: Here is the full strategy: 5 Minute BTC and ETH Micro Arbitrage The system trades short 5 minute Bitcoin and Ethereum contracts In fast markets temporary mispricings appear when YES + NO drops below one dollar The bot scans in real time and captures the spread the moment it appears Speed over emotion When volatility spikes and manual traders hesitate the system reacts automatically Orders execute instantly without delay hesitation or emotional bias By the time most traders understand what happened the opportunity window is already gone Automation compounds the edge Instead of chasing large wins the strategy captures small spreads repeatedly High frequency execution allows the bot to run continuously stacking micro advantages into meaningful returns over time All that is left is refining the code deploying at scale and letting it run

winkle.

171,643 Aufrufe • vor 8 Monaten

A lesson for every Polymarket bot developer: I built a strategy that looked perfect on paper. Backtested it. Looked like a winner. Almost went live. Then i actually measured real costs. Strategy was dead before the first trade. And this is what bot building on Polymarket actually looks like. Here is what happened (and what you MUST know): Backtested mean reversion on crypto dips. SOL came back at +44% return and 70.5% win rate. Beautiful clean curve. Looked ready to ship. Then i measured real round-trip costs on SOL flash dips. Backtest assumed 0.45% in fees and slippage. Reality was 1.44%. Strategy stops working at 0.70%. Starting again. But the lesson was worth more than any profit the strategy could have made. Here is what i actually learned: Taking a dip with a market order means you eat the spread the dip just created. The volatility making your signal is the same volatility destroying your fill. You see the opportunity. You enter. You already lost. But resting a limit order below market and letting the dip come to you? You collect the maker rebate instead. Same thesis. Completely opposite execution. One bleeds money, one prints it. That one realization changed how i think about bot strategy entirely. 180 strategies tested to get there. 179 dead. That is not failure. That is how you find the 5 that actually work. Building a bot on Polymarket is not about finding a magic strategy. It is about eliminating every wrong answer until only the right one is left.

A lesson for every Polymarket bot developer: I built a strategy that looked perfect on paper. Backtested it. Looked like a winner. Almost went live. Then i actually measured real costs. Strategy was dead before the first trade. And this is what bot building on Polymarket actually looks like. Here is what happened (and what you MUST know): Backtested mean reversion on crypto dips. SOL came back at +44% return and 70.5% win rate. Beautiful clean curve. Looked ready to ship. Then i measured real round-trip costs on SOL flash dips. Backtest assumed 0.45% in fees and slippage. Reality was 1.44%. Strategy stops working at 0.70%. Starting again. But the lesson was worth more than any profit the strategy could have made. Here is what i actually learned: Taking a dip with a market order means you eat the spread the dip just created. The volatility making your signal is the same volatility destroying your fill. You see the opportunity. You enter. You already lost. But resting a limit order below market and letting the dip come to you? You collect the maker rebate instead. Same thesis. Completely opposite execution. One bleeds money, one prints it. That one realization changed how i think about bot strategy entirely. 180 strategies tested to get there. 179 dead. That is not failure. That is how you find the 5 that actually work. Building a bot on Polymarket is not about finding a magic strategy. It is about eliminating every wrong answer until only the right one is left.

Oracle Boar

14,379 Aufrufe • vor 7 Monaten