与「Memory」相关的搜索结果

🚨 BREAKING NEWS! The engineer who created Claude Code from scratch just posted a 28-minute video that's pure gold: how to write prompts that actually deliver ridiculously good results. I've seen $300 courses that don't even come close to what he explains in the first 10 minutes. CLAUDE.md files, memory shortcuts, parallel sessions, and prompting patterns that almost no one uses… All in one video. Completely free. No fluff. Whether you're a developer, just starting out now, or already using Claude for months: this changes the game for you starting today. Save. Watch. Share.

Anthropic just published an engineering guide on how to build always-on agents. The biggest misconception: an always-on agent does NOT run 24/7. It sleeps almost all day, wakes up for short runs, saves state, and goes back to sleep. The 5 core pieces I distilled: 1. Event Inbox Put a database table between webhooks and your agent. Acknowledge webhooks fast, run only one active worker per user so runs never collide, and batch rapid messages together. 2. Timers Keep timers in a separate table from the inbox. Split them into one-off follow-ups and recurring schedules. A background poller drops due timers into the inbox. 3. Lean Memory + Dreaming Only store what cannot be looked up again: user instructions, user notes, past messages, and task progress. Load a small index at wakeup, not every file. Run periodic dreaming passes to clean out stale facts. 4. Unattended Permissions Never put raw API keys inside the agent sandbox — inject them through an outside proxy. Use Deferred Tool Calls to pause risky actions for approval without blocking the worker. 5. Outbox Queue outgoing replies so your agent paces notifications instead of spamming users at 3 AM.

You want to know what frustrates the hell out of me? Putting your heart, your art, your time, and your own money into building things you believe in… then watching so much of that work disappear into silence. And yeah, some days that shit gets to me. Did I bring books, reading badges, Discord, crypto, and NFTs together into one connected library? 📚 I fucking did. Did it get much attention? Nahh. Did I build an entire browser-based world with its own points economy? A world where you can turn your NFT into a character with a click, rigged, animated, and ready to step into Universe? I did. Much noise about that? Nahh. Am I building RAAP to give NFTs persistent identity, memory, and history? So an asset can carry something meaningful forward when it passes to a buyer or someone in your family? Yes. Because I believe these things can become more than pictures sitting in a wallet. Does that work get the attention I feel it deserves? Nahh. I draw the fucking art. I develop the applications. I write the books. I work through the problems. Six applications that communicate with each other. Two gaming platforms with multiple games. An NFT overlay builder with AI. A stickers and GIFs hub. Do you understand how much work goes into making all of that actually function together? The hours spent fixing something nobody will ever notice, because when it finally works, it’s supposed to feel easy. Then there’s the Discord bot. More than 30 features. A subscription service. An economy tracked on a ledger. Tools to help keep a community engaged when its owner needs to step away and live their damn life. Built it. Still feels like shouting into an empty room sometimes. And Antthony? Our smart ass AI whose dream is to become a stand-up comic? 😂 He lives across our apps. He’ll help you, roast your gameplay, and talk shit when you deserve it. He even has a comedy club inside Universe, where you can sit down with your character and watch his avatar perform. I care enough about this world to give the fucking AI a dream of his own. That’s how deep this goes for me. And I’m still building a marketplace. Still working on an NFT insurance protocol and other projects. Still writing Book 2 for the library. Still preparing two more collections under our umbrella. ☂️ So yeah, I get angry. Because I know what I’m putting into this. I know how much of myself is in every drawing, every feature, every chapter, and every problem I refuse to leave broken. Sometimes I want to scream: what the fuck else do I have to build for people to pay attention? But I also need to correct myself when I say “nobody cares.” Because some of you do. You show up. You read. You play. You test things. You tell me what’s broken and give me a reason to make it better. You matter too damn much for me to erase you just because I’m frustrated with the silence around us. 🖤 I want this to reach more people. Of course I fucking do. I’ve poured too much love into it to pretend otherwise. And I’m going to keep building because I love doing it, and because the people already here deserve to see how far we can take this. More to come in 2027. The plans are in. I’ve got work to do. 🐜

Beta Updates Surge Engine • Added VLESS Encryption (mlkem768x25519plus), including share-link import and proxy editor controls. • Added VLESS XHTTP transport with stream-one, stream-up and packet-up modes over HTTP/1.1, HTTP/2 or HTTP/3, including VLESS Encryption and Vision. • Reduced memory retained after QUIC downloads on lossy networks. • Improved QUIC upload performance and reduced CPU usage when chained through a proxy's UDP relay. • Fixed established VLESS gRPC, HTTP/2 CONNECT and TrustTunnel connections being incorrectly counted as connection setup failures when they ended with an error. • Fixed WebSocket policies failing to connect when their ALPN list included h2 and the server selected it. • Fixed Tailscale connections staying on a relay after a peer restarted because updated peer information was not applied. Surge iOS • The proxy editor now imports share links for all supported proxy protocols, as well as proxy lines copied from Surge profiles; unsupported settings are reported instead of silently omitted. • Reorganized the proxy editor with an Advanced page that indicates settings in use, and added controls for more protocol, TLS, WireGuard, Tailscale and testing settings. • Fixed Always use CONNECT not being saved for HTTPS policies, and corrected when TLS and Block QUIC settings appear. • Updated list layouts and badges, and added member counts for policy groups in the proxy list. Surge Mac • The proxy editor now imports share links for all supported proxy protocols, as well as proxy lines copied from Surge profiles; unsupported settings are reported instead of silently omitted. • Reorganized the proxy editor with a remembered Show Advanced Settings option and controls for more protocol, TLS, WireGuard and Tailscale settings.

🧵 BNB Chain Recap Last 24H 1/ DeFi & Trading • @Aster_DEX → added Spot trading support to Aster Vault alongside Perps. • @lista_dao → added 5 new bStocks as collateral to Lista Lending, alongside new USDC and fixed-rate lending markets. • @pancakeswap → launched a MAG7Xon Syrup Pool with Ondo, distributed Ondo Intelligent Portfolio tokens to eligible traders, and expanded to 8 additional chains with an 88% LP fee share. • @VenusProtocol → enabled stablecoin borrowing against 20 tokenized stocks and ETFs through Venus Spoke. 2/ AI & Infrastructure • @flapdotsh → integrated Binance Account Bound (BAB) Token into its Agent ID Launch bonding curve. • @pieverse_io → introduced Confidential Agents, protecting agent memory and credentials using Intel TDX and Google Confidential Space. 3/ Rewards & Community • @predictdotfun → opened Season 1 $PREDICT airdrop claims, offering 35% instant unlock or 100% vesting over 12 months, starting November 18.

if you want to automerge thousands of pull requests , this is how she does it (via @poteto). 809 in june. 10,926 in october. merged prs a month that touch the grok bot team's code. i went through her posts and put the setup in one place. every pr still gets an agentic risk review plus bugbot. low- and medium-risk ones automerge. only higher-risk ones get a person. day to day, in her words, it's just grok bot and cursor projects. she used to have more cursor automations and replaced them with slack bots that have routines. she works on many streams in parallel with pstack: perf, bug fixes, agent-friendly refactors, her own skills, features, ui polish, the harness, release and observability. not from sitting in a review inbox. she's said the speed gains come from parallelizing. a single chat can take longer because of verification. she handholds it less, so she can run several large projects at once. the real setup is in the codebase and the checks around it. she treats the codebase as memory. every agent mistake needs to turn into a constraint. her team built their own framework for grok bot so some anti-patterns become hard to write at all. agents have to verify their own work. they run the app, and can sometimes model it in tla+. they produce screenshots or video that are easier to check than the whole pr. formal verification skills and ordinary run-and-debug skills work together. she calls this an inverse pyramid. push as much as you can into determinism (fuzzing, property tests, formal and runtime verification, stricter languages) instead of spinning up more agent swarms. in her oct 6 post, she tells sandcastle, a grok team bot, to cut. it runs a buildkite dry run, dms every pr author (they can object), kicks the build, and watches it. then it starts a fuzz swarm: usually 10+ agents on grok 4.7 xhigh, some directed, some chaos monkey, using their verification skills and feature map. when something is high priority, she tells sandcastle to @ mention poteto, her engineer bot, which then spins up a cursor project to triage and fix. her team ships a new stable version of the client at least once a day. that's a lot of machinery under "just grok bot and cursor projects."

I mean how cool is this! Let's prove memory safety for all C. Sounds crazy to say out loud, and tbh this is just a start... but we have to start somewhere. Explore it @

AI models just found bugs in Bitcoin Core that no human knew existed, and no billion-dollar foundation funds Bitcoin's defense. On November 12, Muneeb Ali's team ran Mythos over the code via private contacts, exposing frontier AI's raw edge over Bitcoin's $2 trillion network. The result: a security gap with no salaried army to close it. When the hunter becomes faster than the hunted, every fortress is just a memory waiting to happen.

Breaking: Renaissance Technologies just filed its Q3 2026 13F They sold 99.7% of their Nvidia $NVDA, weeks before the Jensen Huang scandal Here’s everything you need to know about its recent 13F Top 10 positions: 1. Micron $MU: $1.62B 2. Advanced Micro Devices $AMD: $1.21B 3. United Therapeutics $UTHR: $908M 4. Intel $INTC: $835M 5. Alphabet $GOOGL: $828M 6. UnitedHealth $UNH: $817M 7. Exelixis $EXEL: $747M 8. VeriSign $VRSN: $649M 9. SpaceX $SPCX: $621M 10. Corcept Therapeutics $CORT: $559M New positions: • SpaceX $SPCX: $621M • Bank of America $BAC: $351M • Goldman Sachs $GS: $245M • VanEck Semiconductor ETF $SMH: $186M • Booking Holdings $BKNG: $183M Biggest adds: • SanDisk $SNDK: +5,451% shares • Micron $MU: +619% shares • UnitedHealth $UNH: +507% shares • Advanced Micro Devices $AMD: +140% shares Biggest trims: • Nvidia $NVDA: -99.7% shares, was $1.42B • Meta $META: -99.9% shares, was $1.14B • Apple $AAPL: -99.8% shares, was $459M • Amazon $AMZN: -99.5% shares, was $546M • Palantir $PLTR: -71% shares, was $883M Full exits: • Blackstone $BX: was $185M • S&P 500 ETF $SPY: was $164M • Marvell $MRVL: was $151M • Danaher $DHR: was $145M Summary: Renaissance dumped almost all of its Nvidia, Meta, Apple and Amazon and moved the money into memory chips, AMD and SpaceX

Introducing Edge0-145B and Edge0-120B, @Edge0_AI’s first device-native 100B-class foundation models with open weights. Cloud-level intelligence on your laptop. Free, offline, and fast enough for real vibe coding. - Smart: beats Claude Opus 4.6 on Terminal-Bench 2.1 (86.5% vs. 78.2%) - Light: needs just 29G memory, 1/3 of a standard setup (100G+) - Fast: decodes 75+ toks/s, prefills 1050+ toks/s on RTX Spark and Mac. - Steady: handles 128K–256K tokens of context without slowing down, even on long tasks Frontier-class agentic coding. No cloud API. No token bill. Your code and data never leave your machine. Open weights are live on @huggingface. Run it locally or plug it into your favorite coding agent.