Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Most agentic workflows die a slow death from cost creep before they ever finish the job. SenseTime's new Token Plan flips that: complex multi-step tasks now run at ~60% lower token cost, and for the first month you get 1,500 calls refreshing every 5 hours — free. That's enough...

21,461 Aufrufe • vor 3 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Anthropic dropped 33 pages for Claude trading bots Last night I decided to try writing one and it worked out for me In 10 hours this script made me $561 The bot has a win rate of about 71% Wallet: Copytrade: Here is the full strategy: The system builds automated workflows for Claude by packaging domain expertise into structured skills that activate automatically when relevant tasks appear Skill architecture Each skill is structured as a modular package containing instructions, scripts, and reference materials This allows Claude to apply specialized workflows without requiring the user to repeat instructions in every conversation Progressive context loading Skills follow a three-layer architecture where only minimal metadata is loaded initially Full instructions and supporting files are accessed only when needed, reducing token usage while maintaining specialized expertise Trigger detection Skills activate when the user request matches defined trigger phrases or workflows This ensures the correct workflow loads automatically without requiring manual prompting Workflow execution Once activated, the skill executes a predefined multi-step process These workflows can include data analysis, document generation, automation scripts, or coordination across external tools Consistency and reliability Because workflows are encoded directly in the skill instructions, Claude performs tasks using consistent methodology rather than ad-hoc prompting Testing and iteration Skills are continuously refined through triggering tests, functional validation, and performance comparisons to ensure reliable execution Automation edge Instead of solving tasks from scratch each time, the system repeatedly applies optimized workflows Over time this dramatically reduces prompt complexity, improves output consistency, and scales productivity across thousands of tasks

winkle.

334,453 Aufrufe • vor 4 Monaten

Claude can make your own money printer That is exactly what happened to me I wrote my own script It took me 6 hours On the very first night the bot made $2,705 profit Copytrade: Wallet: Here is the full strategy: The system builds automated workflows for Claude by packaging domain expertise into structured skills that activate automatically when relevant tasks appear Skill architecture Each skill is structured as a modular package containing instructions scripts and reference materials This allows Claude to apply specialized workflows without requiring the user to repeat instructions in every conversation Progressive context loading Skills follow a three layer architecture where only minimal metadata is loaded initially Full instructions and supporting files are accessed only when needed reducing token usage while maintaining specialized expertise Trigger detection Skills activate when the user request matches defined trigger phrases or workflows This ensures the correct workflow loads automatically without requiring manual prompting Workflow execution Once activated the skill executes a predefined multi step process These workflows can include data analysis document generation automation scripts or coordination across external tools Consistency and reliability Because workflows are encoded directly in the skill instructions Claude performs tasks using consistent methodology rather than ad hoc prompting Testing and iteration Skills are continuously refined through triggering tests functional validation and performance comparisons to ensure reliable execution Automation edge Instead of solving tasks from scratch each time the system repeatedly applies optimized workflows Over time this dramatically reduces prompt complexity improves output consistency and scales productivity across thousands of tasks

winkle.

53,951 Aufrufe • vor 4 Monaten

Most recent diffusion language model research (that I’ve seen) seems to be using masking as the noising process. It looks like, however, most closed-source models (Google Gemini Diffusion and possibly Inception Labs’ Mercury) use a different noising process, where instead of masking tokens, they replace them with different tokens (either with a random token or a semantically similar token). I wondered how they were getting such high throughput with the latter noising process, since I believed that optimizing inference with KVCache approximation would be more difficult (for various reasons). I visualized this noising process with tiny-diffusion and compared it to normal unmasking, and was very surprised to see how fast the generation “settles” into a reasonable output, and then only slightly refines afterwards, requiring much fewer steps in total. Unmasking (where tokens are never remasked, the typical implementation) is inherently limited in generation speed by the fact that an increase in tokens decoded per step leads to more errors due to the mismatch between individual and marginal token probability distributions we sample from. The token replacement noising process seems to have a much different set of characteristics. Because we sample each token per step, every token makes “progress” towards the final output each iteration (in addition to *potentially* giving other tokens more information in future steps). Generally, masking has outperformed other noising processes, which is probably why most research focused on it (using smaller models). But the paper referred to in the retweet shows that random replacement as a noising process may scale better as model size increases. Big labs might have noticed these results much earlier (due to having drastically more training resources and being able to test larger models), which may explain the discrepancy in the choice of noising process. I’m gonna test this with larger models, since tiny-diffusion only has 10M parameters.

nathan (in sf)

40,440 Aufrufe • vor 6 Monaten

Claude Code Agent Teams are f*cking ridiculous 🤯 One prompt → a team lead breaks your project into pieces, spins up multiple AI agents, and they all work on different parts simultaneously. Research, builds, reviews, and debugging: all happening at the same time. All inside Claude Code. If you're running complex projects where every step waits on the last one... Agent teams eliminate the entire bottleneck: → Tell Claude what you need and describe the team structure in plain English → A lead agent breaks the work into a shared task list → It spawns 3-5 teammates — each with their own context and workspace → Teammates research, build, test, and review in parallel → They message each other, share findings, and challenge each other's work → The lead synthesizes everything into a finished deliverable No managing agents yourself. No waiting for step 1 to finish before step 2 starts. No single-lens reviews that miss half the issues. What you get: → Competitive research across 5 brands done in minutes instead of hours → Multi-component builds where frontend, backend, and data layers happen simultaneously → Creative reviews from 3 different angles at once — brand voice, conversion, differentiation → Funnel debugging where 4 agents investigate 4 theories and debate until they find the real answer Built 100% in Claude Code with one settings change. I put together a full DTC playbook: 5 workflows with copy-paste prompts, the exact setup process, token management tips, and honest guidance on when agent teams are worth it vs. when a simpler approach is the better move. Want it for free? > Like this post > Comment "AGENTS" And I'll send it over (must be following so I can DM)

Mike Futia

46,384 Aufrufe • vor 4 Monaten

There’s a reason the LimeWire name still hits people instantly. If you were around in the early internet days, LimeWire was everywhere. Music discovery, file sharing, chaos, excitement. It shaped how a whole generation interacted with the web. That kind of brand memory doesn’t fade and LimeWire is proving it can be reused in a serious way. What’s different now is the foundation. LimeWire Network is the decentralized storage layer of LimeWire, built on BNB Chain. It is not a nostalgia project. It is infrastructure. Storage, transfers, and usage are happening on chain, designed to scale for real applications rather than demos. The growth backs that up. Looking at recent data on lmwrscan, LimeWire Network has already moved into tens of terabytes of stored data, with tens of thousands of uploads and consistent daily activity. Network usage keeps climbing, not spiking once and disappearing. That kind of curve usually shows real users, not incentive farming. And the economics are clear. The $LMWR token sits at the center of the system. Users pay in LMWR to use storage. Node operators earn LMWR for providing resources. Rewards and payments stay inside the ecosystem instead of leaking out to third parties. That loop matters. Most decentralized storage networks struggle because nobody knows they exist. LimeWire doesn’t have that problem. The brand alone opens doors, pulls attention, and lowers the friction for new users to try the product. When you combine that with live usage data and a functioning token economy, the upside starts to look asymmetric. Built on BNB Chain, LimeWire Network also gets the scalability needed if adoption keeps accelerating. That choice signals intent to grow, not just experiment. This feels like a rare case where nostalgia is not the product, it is the distribution layer. Curious how you see it. Are you watching LimeWire because of the brand comeback, the LimeWire Network growth, or the role of the LMWR token in the long run?

ryu 龙

25,416 Aufrufe • vor 5 Monaten

1/7 Built a Polymarket trading bot over 3 months. Here are the biggest mistakes that cost me real money > Went from v1 to v61. Every version fixed something painful. --- 2/7 Stop Loss killed more money than it saved. > Binary markets need room to breathe - fluctuations are normal. > Stop Loss was cutting positions on random noise and locking in losses right before the market flipped. > Removed it in v61. Immediately better. --- 3/7 Martingale + Stop Loss = a loss cascade. > Seemed logical: lost $5 -> bet $8, lost again -> bet $10. > In practice: a losing streak plus early exits = a hole in your balance in a single day. > Killed it. For good. --- 4/7 Smart Exit without Force Exit is a trap. > Token hits 90c (+75% profit), but the bot was waiting for a "BTC reversal" signal. > Market closes, token drops, profit gone. > Fix: hard Force Exit at 85c. No conditions, no waiting. --- 5/7 Blocking the 5:30-10:30 PM ET window felt safe. It wasn't. > NYSE open = sharp spikes = bad signals. Made sense to block it. > But the full block was also killing clean entries at 8-10:30 PM. > Had to split the zone into segments with different edge/move thresholds. --- 6/7 The Gamma API lies about market start time. > Start price ("price to beat") is the core input for every signal. > Gamma was returning stale data. Had to pull prices directly from Chainlink on-chain on Polygon. > That's its own adventure - polling a smart contract every 2 seconds at 2 AM. --- 7/7 The real lesson: don't overcomplicate what works. > v1: complex system, 10 indicators -> -$200/day > v61: "buy the expensive token for $5, exit at +30%" -> consistently green > Simpler logic = fewer failure points. > The bot runs 96 intervals a day. Every mistake shows up fast.

Kotte

31,753 Aufrufe • vor 3 Monaten