Mentions
Conversations linking to GitHub, newest first. Times are UTC.
Mentions by source
X
Bluesky
Hacker News
V2EX
Qiita
DEV
Mastodon
Latest posts
StandUp Pal 1.2 ☁️ Your fitness pet now follows you between Macs: settings, reminders, XP and streaks sync through iCloud Drive. No login, no server. Two Macs in one day? XP adds up, nothing gets overwritten 💪 github.com/deus42/standup-pal/releases/tag/v1.2.0 t.co
@catalinmpit Amazing Catalin! Would love your feedback on Beacon, let me know what you think :) Asymptote-Labs/agent-beacon
I recompiled Super Mario Odyssey to run natively on PC - Power Moon Recomp (open source, up to 4K, mods, no emulator) Power Moon Recomp is a native PC port of Super Mario Odyssey made by static recompilation: the game's Switch code is translated to C ahead of time and compiled into a regular Windows program. No emulator runs while you play, the Switch parts the game talks to (graphics, audio, input, files) are reimplemented on the PC, with Vulkan for graphics. What works - The whole game, start to finish - Any resolution: 1080p, 1440p, 4K and beyond, or lower with AMD FSR 1 for weaker PCs; SMAA - Keyboard and controller, every button remappable - Mods that replace game files (costumes, models, textures, music), with an in-game Mods menu - Windows and Linux now, macOS also coming soon What you need Your own copy of Super Mario Odyssey version 1.0.0, dumped from your own Switch (exefs + romfs). Credits: built on LAS Recomp by Peiikai, with names from the OdysseyDecomp project. Built with heavy help from an AI coding agent (Claude), directed and tested by me. Download: gitlab.com (My Github account got banned instantly after uploading the project, so it is hosted on GitLab now.) Edit: Version 0.1.6 is out. Stuttering should be a lot better now. The game saves every shader it compiles, and shaders it has already loaded get prepared before the game starts, so you might see a small "Preparing shaders" window for a few seconds. It also fixes a bug where RAM usage could climb to over 20 GB after you'd played for a while. There's a Linux .AppImage file now too. The first visit to a new area can still hitch a bit. Feedback is welcome!
"Age verification" is quietly turning into "upload your passport."More and more services ask for a full ID scan or a selfie just to confirm you're over 18. The question needs one bit. The scan hands over your name, photo, date of birth and document number, and it ends up stored by the site or a ve "Age verification" is quietly turning into "upload your passport." More and more services ask for a full ID scan or a selfie just to confirm you're over 18. The question needs one bit. The scan hands over your name, photo, date of birth and document number, and it ends up stored by the site or a vendor. And it leaks. Last October, Discord confirmed that about 70,000 government ID photos, uploaded for age checks, were exposed through a support vendor. There's a better credential already in your pocket: the chip in your passport or ID card, signed by your government. zkagent uses it: → your phone reads the chip and checks the government's signature → the site asks one question: "over 18?" → it gets yes or no, nothing else → no upload, no photo, no copy of your document anywhere It can also answer "one person, one account" per site without saying who you are. And for government services, KYC and similar checks, it answers yes/no questions about the document ("valid for 6 more months?", "does the name match?") without the site ever seeing it. It works today on Android, open source under Apache-2.0. Take it, change it, run your own. You don't have to start from scratch. Honest limits: tested on one phone and two documents so far, and it's minimal disclosure, not zero-knowledge. hamr0/zkagent
中兴 F50/MU3350S 刷 OpenWrt: maybe-kefka/mu3350s-openwrt 机器锁 BL、没 root,mu300-linux 默认设备已有 su,直接跑卡在 root 这步,只能自己补 root 通道 + B04 AVB 补丁 + 安装器适配,另加 Clash Meta 分流面板。 全程 DSH + deepseek-v4.1-flash 开发,需要者直接把仓库丢给 agent #OpenWrt #ZTE
VoxScribe update: offline dictation that now spells names from your screen and learns from your fixes VoxScribe is a free, open source voice dictation app for Windows and Android. You hold a key on Windows (F9 by default) or tap a floating button on Android, talk, let go, and the text is typed straight into whatever app you are using. The speech model runs on the device, so your voice never leaves your computer or phone and it works with no internet at all. There is an optional Pro upgrade, a one-time $14, no subscription. What’s new since the last post. The Android app now has term packs for medical, legal and business words, so drug names and legal terms come out spelled right, plus “Teach your voice”, where you read a few sentences and it learns the words it gets wrong for your accent. There is also a Quick Settings tile to start dictating from the notification shade, and a read it back option so you can hear what was typed without looking. On Windows, the latest version adds a choice of speech models, including bigger ones for better accuracy. What’s coming in the next Android update, already working on my test phone. Screen-aware spelling: when you dictate a reply, names and product words already on the screen fix how they are spelled, so a message to Kateryna doesn’t come out as Katerina, and “whatsapp” comes out as WhatsApp. Learns your words: fix a misheard name by hand once and it is spelled your way every time after. And speak once, fill the whole form: say “name Sam Lee, phone 555 0100, email sam at mail dot com” and every box on the form fills at once. All three run offline like the rest of the app. The numbers so far: around 770 downloads across both platforms and the first two paying customers, both of whom found it on their own. Feedback I’d love: which of these would actually make you switch from the dictation you use today, and what is still missing that keeps you typing instead of talking? ahmedhmam1994/voxscribe-ai-voice-dictation
اتمنى الي يجربة يصور فيديو لاني حاسد حقين LG حاليا. stremio-origin/webos
El repositorio es MiroFish: 666ghj/MiroFish
画像生成はおいておいて、ローカルで無課金GPTより良いものが動くかもしれないので、Strataは注目しておくといいかもしれません ゲーミングPCなら試してみるのもよし Niko1221/Strata
@JohnsTechDev @herdrdev the icons dont, but the dot color changes. any "needs you" will also create a notification that'll be visible as well as increment the badge on the bell icon github.com/shellscape/herdr-whitby/blob/main/prev…
@pierin0lartista @rgm79kunio qurataro/sonson Hai già scaricato la patch IPS, ma è anche possibile scaricarla da GitHub.
@arisinvestor give it a try =) I open sourced it 0xProbabillity/claudeberry
Para quien le interesen los detalles técnicos, la aplicación está hecha en Rust. Para que suene la música se ejecuta un webview oculto con el SDK de Spotify, ya que por limitaciones no encontré otra forma «correcta» de hacerlo La aplicación está en GitHub nuzkito/melodia
@skdh Here is theory based on my assumptions and AI answers, just for fun osf.io github.com/rakovpublic/CCDR/blob/master/Synthesis…
Para quien le interesen los detalles técnicos, la aplicación está hecha en Rust. Para que suene la música se ejecuta un webview oculto con el SDK de Spotify, ya que por limitaciones no encontré otra forma «correcta» de hacerlo La aplicación está en GitHub nuzkito/melodia
For those who don't want AI ports, HakuX is running VERY WELL as an emulator (Mediatek g57) rfandango/hakuX
Location: Brazil (UTC-3) Remote: Yes. Happy to overlap substantially with US/Canada, European, Australian or New Zealand working hours. Willing to relocate: No Technologies: Python | LangGraph | LangChain | Graphiti/Neo4j | RAG/graphRAG | PyTorch/HuggingFace | n8n | AWS | Terraform | Docker | FastAPI | PostgreSQL | React/Next.js | MCP | Claude Code and Codex (with engineered harnesses, solid human judgement and experience arguing with them–I don't do free-rein hype-guy autonomous coding) Résumé/CV: General tech: drive.google.com Health/clinical/biomed domain-specific: drive.google.com GitHub: github.com/prodm93 Whitespace demo (frontend accessibility still needs work): drive.google.com Email: prman.hn@proton.me AI engineer, agentic systems builder and former biomedical researcher. I have 5+ years of development experience and 4+ years building AI systems professionally across startups and larger corporate clients, with work spanning biomedical/clinical AI, finance, content systems, automation and general-purpose LLM applications (including regulation- and compliance-heavy domain work). The common thread is probably best described as "grounded mad scientist" energy–with explicit focus on the 'grounded' bit. I like getting dropped into problems where there is no roadmap, the inputs are horrible, the requirements are fuzzy and the straightforward-looking solution stops being straightforward approximately fifteen minutes after you touch the real data. I tend to do my best work somewhere around that point. A few examples: For a long-term startup client, I effectively became the technical founding person with no repo, no technical guidance and no roadmap in sight. Among other things, I built their AI-driven content and automation ecosystem from scratch. When generic AI output became the problem, I came up with an in-place DPO approach that mined their actual messy Notion editing history, including highlights, strikethroughs and collaborative edits, to generate positive/negative preference pairs for few-shot prompting. No labellers and no fine-tuning. A/B testing, which I also designed for non-technical founders, showed more than 30% improvement in output quality. For Danaher Corporation via NILG.ai, I built a pharmaceutical pipeline extracting clinical endpoints from FDA drug labels and ClinicalTrials.gov records, then classifying them into higher-level outcome categories. The extraction itself was the easy bit. The interesting work started when the FDA API confidently returned the wrong drug label, source datasets had gaps and seemingly simple client terminology turned out to be inconsistent enough to silently poison downstream analysis. A lot of my work is exactly this: translating fuzzy human requirements into technical systems that are not merely impressive-looking, but actually trustworthy. For Berkshire Partners, I built a private long-context retrieval and summarisation system over confidential 120-page interview transcripts using locally-run open-source models. This was early 2024, under severe context-window constraints, so I adapted LangChain's refine chain across multiple retrieval rounds to preserve information while generating higher-order outputs such as market forecasts and investment opportunities. Roadmap? Nowhere to be seen. I also recently had a feature PR merged into Backblaze's open-source genblaze SDK. The docs told users in several places to hash fetched assets themselves for provenance verification, but no shipped tool actually did it. I added opt-in byte-level verification through the existing SSRF-hardened transfer path with DNS pinning, presigned URL credential redaction and per-asset failure isolation. What I enjoyed most was dropping into an unfamiliar codebase, figuring out why earlier architectural decisions had been made and building around those constraints instead of bulldozing through them. I started my AI engineering career at an AI + NLP research startup called Sagewrite (before the ChatGPT hype took off), where I built substantial chunks of their production backend. I worked on scientific PDF parsing and text-processing pipelines, prepared model-training datasets and built scientific text-generation systems using models including GPT-2. So yes, I've been trying to get useful things out of AI slop since GPT-2, which had approximately the literacy of a toddler–work in this field is not a fad pivot for me! Building cool stuff is great, but I also care about robustness. I recently single-handedly wrangled an unexpected security incident during a short contract where it wasn't quite my purview. Love building products, and also love taking care of the ecosystem around it. As an erstwhile scientist, I also come with extensive biomedical research experience. My wet-lab background is in immunology, immunotherapy and cancer biology, including doctoral work at Amsterdam UMC and MSc research at CIC BioGUNE that contributed to a Nature Communications paper on Siglec-15. Since moving into AI, I have worked on pharmaceutical and clinical-trial pipelines, PubMed/citation analysis, therapeutic chatbot systems, RAG over biomedical literature and antiviral drug-discovery ML. I am very interested in biomedical/healthtech AI, but absolutely not limited to it. Outside client work, I am currently building Whitespace, a React/Next.js app that maps a user's professional expertise against the patent landscape to surface unmet needs and generate validated R&D ideas. It uses agentic graphRAG, multi-agent workflows, an adversarial multi-LLM council and human-in-the-loop review. The backend is being built as a proper production system rather than a demo held together with hope: Terraform-defined AWS infrastructure, LangGraph workflows, async orchestration, observability and a lot of thought around security. Demo videos/screencaps linked above. The other useful thing to know about me is that I learn obscenely fast. My brain usually has about 2048 tabs open, most involving some Google rabbit hole, documentation page or StackOverflow thread explaining why the thing that "should obviously work" does not. I use AI heavily in my coding workflow too, but I am perfectly happy arguing with it until I understand why a design is sound rather than accepting whatever compiles. Logistics: I work through Confluente Ltda, my registered Brazilian PJ entity. For overseas companies this can be structured as a straightforward B2B vendor relationship rather than foreign payroll or visa sponsorship. Day to day, I show up, do the work and remain accountable like any other member of the team. Administratively, there is much less cross-border employment machinery for you to deal with. I have worked remotely with clients across multiple continents and time zones for years, including long-running engagements, so async work and deliberate communication are very normal for me. Friendly and professional, looking for same. Open to full-time, part-time or long-term contract arrangements–but preference for something long-term and stable. Special place in my heart for founding eng roles. Interested in AI/ML engineering, agentic systems, AI-native software development, automation, applied AI and biomedical/healthtech AI.
REA vs LeanREA: AI Reverse Engineering in Real Games REA gives an AI agent tools to inspect binaries and trace evidence. LeanREA takes a lighter shell-tool approach. We compare their author-reported benchmark and follow real projects—from Doom and Terraria demos to Touhou 4, DX-Ball, Ledger Reborn, co-op mods, and a Skate 3 × Modern Warfare 2 mashup. The Doom/Terraria timings and LeanREA benchmark are author-reported; we did not rerun them. The Skate × MW2 mashup is a neighboring reverse-engineering project; its authors do not claim it used REA. Touhou gameplay here is illustrative, not the REA case capture. The Terraria REA run reached a metadata limit and switched to ILSpy. CHAPTERS 00:00 Hook and author-made game mashup 00:47 What REA is 01:22 The evidence loop 01:57 LeanREA vs REA: 36-run benchmark 03:13 Chocolate Doom and Terraria demos 03:48 Touhou 4: aim the bullet ring 04:43 DX-Ball: screen position to stereo 05:44 Ledger Reborn: reports to the cent 06:24 Co-op Anything 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 What the tools cannot prove 08:44 Install REA or LeanREA 10:04 What should we reverse next? PROJECTS & SOURCES REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA benchmark: github.com/aicodeking/leanrea/blob/main/bench/BEN… Chocolate Doom/Terraria demo: youtube.com Touhou 4 case study: morluto.github.io DX-Ball case study: morluto.github.io DX-Ball project: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Skate × MW2 mashup: chasmlol/2010-rust-rewrite-mashup Mashup author footage: x.com PhotoCraft clean-room project: storytold/photocraft Music: “Tech Live” by Kevin MacLeod (incompetech.com), CC BY 4.0. License: creativecommons.org Subscribe to RepoSignal for more open-source project deep dives. [ar] REA ضد LeanREA: الهندسة العكسية بالذكاء الاصطناعي في الألعاب الحقيقية تُزوّد REA وكيل الذكاء الاصطناعي بأدوات لفحص الملفات الثنائية وتتبع الأدلة. بينما يعتمد LeanREA على أسلوب أدوات سطر الأوامر المُبسّط. نقارن نتائج الاختبار المعياري التي أبلغ عنها مُطوّروهما، ونتابع مشاريع حقيقية، بدءًا من عروض Doom وTerraria التجريبية، وصولًا إلى Touhou 4 وDX-Ball وLedger Reborn وتعديلات اللعب التعاوني، ولعبة Skate 3 × Modern Warfare 2 المُدمجة. أُبلغ عن أوقات Doom/Terraria ونتائج اختبار LeanREA المعياري من قِبل مُطوّريها، ولم نُعد تشغيلها. أما لعبة Skate × MW2 المُدمجة فهي مشروع هندسة عكسية مُجاور، ولا يدّعي مُطوّروها استخدام REA. يُقدّم عرض لعبة Touhou هنا لأغراض التوضيح فقط، وليس تسجيلًا لحالة REA. وصل تشغيل Terraria باستخدام REA إلى حدّ البيانات الوصفية، فتحوّل إلى ILSpy. الفصول 00:00 دمج لعبة Hook مع لعبة من صنع المؤلف 00:47 ما هو REA 01:22 حلقة الأدلة 01:57 LeanREA مقابل REA: اختبار معياري لـ 36 جولة 03:13 عروض تجريبية للعبة Chocolate Doom و Terraria 03:48 Touhou 4: التصويب على حلقة الرصاصة 04:43 DX-Ball: تحويل موضع الشاشة إلى ستيريو 05:44 Ledger Reborn: التقارير إلى المركز 06:24 أي شيء تعاوني 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 ما لا تستطيع الأدوات إثباته 08:44 تثبيت REA أو LeanREA 10:04 ما الذي يجب أن نعكسه لاحقًا؟ المشاريع والمصادر REA: morluto/rea LeanREA: aicodeking/leanrea معيار LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… عرض توضيحي للعبة Chocolate Doom/Terraria: youtube.com دراسة حالة Touhou 4: morluto.github.io دراسة حالة DX-Ball: morluto.github.io مشروع DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything دمج Skate × MW2: chasmlol/2010-rust-rewrite-mashup لقطات من مُنشئ الدمج: x.com مشروع PhotoCraft في بيئة نظيفة: storytold/photocraft الموسيقى: "Tech Live" من تأليف كيفن ماكلويد (incompetech.com)، رخصة CC BY 4.0. الترخيص: creativecommons.org اشترك في RepoSignal لمزيد من التحليلات المتعمقة لمشاريع المصادر المفتوحة. [bn] REA বনাম LeanREA: আসল গেমে এআই রিভার্স ইঞ্জিনিয়ারিং REA একটি AI এজেন্টকে বাইনারি পরীক্ষা করতে এবং প্রমাণ খুঁজে বের করার জন্য টুল সরবরাহ করে। LeanREA একটি হালকা শেল-টুল পদ্ধতি ব্যবহার করে। আমরা তাদের লেখকের দেওয়া বেঞ্চমার্কের সাথে তুলনা করি এবং বাস্তব প্রজেক্টগুলো অনুসরণ করি—Doom এবং Terraria ডেমো থেকে শুরু করে Touhou 4, DX-Ball, Ledger Reborn, কো-অপ মড এবং Skate 3 × Modern Warfare 2 ম্যাশআপ পর্যন্ত। Doom/Terraria-র টাইমিং এবং LeanREA বেঞ্চমার্ক লেখকের দেওয়া; আমরা সেগুলো পুনরায় চালাইনি। Skate × MW2 ম্যাশআপটি একটি পার্শ্ববর্তী রিভার্স-ইঞ্জিনিয়ারিং প্রজেক্ট; এর লেখকরা দাবি করেন না যে এটিতে REA ব্যবহার করা হয়েছে। এখানে Touhou গেমপ্লেটি দৃষ্টান্তমূলক, REA কেস ক্যাপচারটি নয়। Terraria-র REA রানটি একটি মেটাডেটা সীমাতে পৌঁছানোর পর ILSpy-তে পরিবর্তিত হয়েছিল। অধ্যায়সমূহ ০০:০০ হুক এবং লেখকের তৈরি গেম ম্যাশআপ ০০:৪৭ REA কী ০১:২২ এভিডেন্স লুপ ০১:৫৭ LeanREA বনাম REA: ৩৬-রান বেঞ্চমার্ক ০৩:১৩ Chocolate Doom এবং Terraria ডেমো ০৩:৪৮ Touhou 4: বুলেট রিং দিয়ে নিশানা করা ০৪:৪৩ DX-Ball: স্ক্রিন পজিশন থেকে স্টেরিও ০৫:৪৪ Ledger Reborn: সেন্ট-এ রিপোর্ট ০৬:২৪ যেকোনো কিছু কো-অপ করা ০৭:০৯ Skate 3 × Modern Warfare 2 × Minecraft ০৮:০৪ টুলগুলো যা প্রমাণ করতে পারে না ০৮:৪৪ REA বা LeanREA ইনস্টল করুন ১০:০৪ এরপর আমাদের কী রিভার্স করা উচিত? প্রজেক্ট ও উৎসসমূহ REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA বেঞ্চমার্ক: github.com/aicodeking/leanrea/blob/main/bench/BEN… Chocolate Doom/Terraria ডেমো: youtube.com Touhou 4 কেস স্টাডি: morluto.github.io DX-Ball কেস স্টাডি: morluto.github.io DX-Ball প্রজেক্ট: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Skate × MW2 ম্যাশআপ: chasmlol/2010-rust-rewrite-mashup ম্যাশআপ লেখকের ফুটেজ: x.com ফটোক্রাফট ক্লিন-রুম প্রজেক্ট: storytold/photocraft সঙ্গীত: কেভিন ম্যাকলিওডের “টেক লাইভ” (incompetech.com), CC BY 4.0। লাইসেন্স: creativecommons.org আরও ওপেন-সোর্স প্রজেক্টের গভীর বিশ্লেষণের জন্য RepoSignal-এ সাবস্ক্রাইব করুন। [de-DE] REA vs. LeanREA: KI-Reverse-Engineering in echten Spielen REA stattet einen KI-Agenten mit Werkzeugen zur Binäranalyse und Spurensuche aus. LeanREA verfolgt einen schlankeren Ansatz mit Shell-Tools. Wir vergleichen die von den Autoren angegebenen Benchmark-Ergebnisse und verfolgen reale Projekte – von Doom- und Terraria-Demos über Touhou 4, DX-Ball, Ledger Reborn und Koop-Mods bis hin zu einem Skate 3 × Modern Warfare 2-Mashup. Die Laufzeiten von Doom/Terraria und dem LeanREA-Benchmark stammen von den Autoren; wir haben sie nicht wiederholt. Das Skate × MW2-Mashup ist ein benachbartes Reverse-Engineering-Projekt; die Autoren geben nicht an, REA verwendet zu haben. Das Touhou-Gameplay dient hier nur der Veranschaulichung und ist nicht Teil der REA-Fallaufzeichnung. Der Terraria-REA-Lauf erreichte ein Metadatenlimit und wechselte zu ILSpy. KAPITEL 00:00 Hook und vom Autor erstelltes Spiel-Mashup 00:47 Was ist REA? 01:22 Die Beweisschleife 01:57 LeanREA vs. REA: Benchmark mit 36 Durchläufen 03:13 Chocolate Doom und Terraria Demos 03:48 Touhou 4: Zielen auf den Kugelring 04:43 DX-Ball: Bildschirmposition zu Stereo 05:44 Ledger Reborn: Berichte an die Zentrale 06:24 Alles im Koop-Modus 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Was die Tools nicht beweisen können 08:44 REA oder LeanREA installieren 10:04 Was sollten wir als Nächstes rückgängig machen? PROJEKTE & QUELLEN REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA-Benchmark: github.com/aicodeking/leanrea/blob/main/bench/BEN… Chocolate Doom/Terraria-Demo: youtube.com Touhou 4-Fallstudie: morluto.github.io DX-Ball-Fallstudie: morluto.github.io DX-Ball-Projekt: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Skate × MW2 Mashup: chasmlol/2010-rust-rewrite-mashup Videomaterial des Mashup-Autors: x.com PhotoCraft-Reinraumprojekt: storytold/photocraft Musik: „Tech Live“ von Kevin MacLeod (incompetech.com), CC BY 4.0. Lizenz: creativecommons.org Abonniere RepoSignal für weitere Einblicke in Open-Source-Projekte. [es-US] REA vs LeanREA: Ingeniería inversa mediante IA en juegos reales REA proporciona a un agente de IA herramientas para inspeccionar binarios y rastrear evidencia. LeanREA adopta un enfoque más ligero, basado en herramientas de shell. Comparamos sus resultados de referencia, reportados por sus autores, con proyectos reales, desde demos de Doom y Terraria hasta Touhou 4, DX-Ball, Ledger Reborn, mods cooperativos y una combinación de Skate 3 y Modern Warfare 2. Los tiempos de ejecución de Doom/Terraria y la prueba de rendimiento de LeanREA fueron reportados por sus autores; no los repetimos. La combinación de Skate y MW2 es un proyecto de ingeniería inversa relacionado; sus autores no afirman haber utilizado REA. El gameplay de Touhou que se muestra aquí es ilustrativo, no representa el caso de REA. La ejecución de REA en Terraria alcanzó un límite de metadatos y se cambió a ILSpy. CAPÍTULOS 00:00 Hook y juego creado por el autor (combinación) 00:47 Qué es REA 01:22 El bucle de evidencia 01:57 LeanREA vs REA: prueba de rendimiento de 36 ejecuciones 03:13 Demos de Chocolate Doom y Terraria 03:48 Touhou 4: apuntar al anillo de balas 04:43 DX-Ball: posición de pantalla a estéreo 05:44 Ledger Reborn: informes al centavo 06:24 Cualquier juego cooperativo 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Lo que las herramientas no pueden probar 08:44 Instalar REA o LeanREA 10:04 ¿Qué deberíamos invertir a continuación? PROYECTOS Y FUENTES REA: morluto/rea LeanREA: aicodeking/leanrea Benchmark de LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… Demostración de Chocolate Doom/Terraria: youtube.com Estudio de caso de Touhou 4: morluto.github.io Estudio de caso de DX-Ball: morluto.github.io Proyecto DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Mashup de Skate y MW2: chasmlol/2010-rust-rewrite-mashup Vídeo del autor del mashup: x.com Proyecto de sala limpia de PhotoCraft: storytold/photocraft Música: «Tech Live» de Kevin MacLeod (incompetech.com), CC BY 4.0. Licencia: creativecommons.org Suscríbete a RepoSignal para más análisis en profundidad de proyectos de código abierto. [fr-FR] REA vs LeanREA : Rétro-ingénierie par IA dans les jeux réels REA fournit à un agent d'IA des outils pour inspecter les fichiers binaires et retracer les preuves. LeanREA adopte une approche plus légère, basée sur un outil en ligne de commande. Nous comparons leurs performances de référence, telles que rapportées par leurs auteurs, et suivons des projets réels : des démos de Doom et Terraria à Touhou 4, DX-Ball, Ledger Reborn, des mods coopératifs et un mashup Skate 3 × Modern Warfare 2. Les temps d'exécution de Doom/Terraria et les performances de LeanREA sont fournis par leurs auteurs ; nous ne les avons pas reproduits. Le mashup Skate × MW2 est un projet de rétro-ingénierie connexe ; ses auteurs n'affirment pas avoir utilisé REA. La séquence de gameplay de Touhou présentée ici est à titre d'illustration et ne correspond pas à la capture d'écran de REA. L'exécution de Terraria avec REA a atteint une limite de métadonnées et a basculé vers ILSpy. CHAPITRES 00:00 Jeu hybride original et créatif 00:47 Qu'est-ce que REA ? 01:22 La boucle de preuves 01:57 LeanREA vs REA : benchmark sur 36 exécutions 03:13 Démos de Chocolate Doom et Terraria 03:48 Touhou 4 : viser avec le cercle de balles 04:43 DX-Ball : de la position de l'écran à la stéréoscopie 05:44 Ledger Reborn : des rapports au centime près 06:24 Coopération à gogo 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Ce que les outils ne peuvent pas prouver 08:44 Installer REA ou LeanREA 10:04 Quel processus inverser ensuite ? PROJETS ET SOURCES REA : morluto/rea LeanREA : aicodeking/leanrea Benchmark LeanREA : github.com/aicodeking/leanrea/blob/main/bench/BEN… Démo Chocolate Doom/Terraria : youtube.com Étude de cas Touhou 4 : morluto.github.io Étude de cas DX-Ball : morluto.github.io Projet DX-Ball : N0zoM1z0/dx-ball Ledger Reborn : lxistired/ledger-reborn Co-op Anything : cranebeaker/coop-anything Mashup Skate × MW2 : chasmlol/2010-rust-rewrite-mashup Vidéo de l'auteur du mashup : x.com Projet PhotoCraft : storytold/photocraft Musique : « Tech Live » de Kevin MacLeod (incompetech.com), CC BY 4.0. Licence : creativecommons.org Abonnez-vous à RepoSignal pour découvrir des analyses approfondies de projets open source. [hi] REA बनाम LeanREA: असली गेम्स में AI रिवर्स इंजीनियरिंग REA एक AI एजेंट को बाइनरी फ़ाइलों का निरीक्षण करने और साक्ष्य खोजने के लिए उपकरण प्रदान करता है। LeanREA एक हल्का शेल-टूल दृष्टिकोण अपनाता है। हम उनके लेखक द्वारा रिपोर्ट किए गए बेंचमार्क की तुलना करते हैं और वास्तविक परियोजनाओं का अनुसरण करते हैं—डूम और टेरारिया डेमो से लेकर तोहो 4, DX-बॉल, लेजर रीबॉर्न, को-ऑप मॉड्स और स्केट 3 × मॉडर्न वॉरफेयर 2 मैशअप तक। डूम/टेरारिया का समय और LeanREA बेंचमार्क लेखक द्वारा रिपोर्ट किए गए हैं; हमने इन्हें दोबारा नहीं चलाया। स्केट × MW2 मैशअप एक संबंधित रिवर्स-इंजीनियरिंग परियोजना है; इसके लेखकों का दावा नहीं है कि उन्होंने REA का उपयोग किया है। यहां तोहो गेमप्ले केवल उदाहरण के लिए है, REA केस कैप्चर नहीं। टेरारिया REA रन मेटाडेटा सीमा तक पहुँच गया और ILSpy पर स्विच हो गया। अध्याय 00:00 हुक और लेखक द्वारा निर्मित गेम का मिश्रण 00:47 REA क्या है 01:22 साक्ष्य चक्र 01:57 LeanREA बनाम REA: 36-रन बेंचमार्क 03:13 चॉकलेट डूम और टेरारिया डेमो 03:48 तोहो 4: बुलेट रिंग को निशाना बनाना 04:43 DX-बॉल: स्क्रीन पोजीशन से स्टीरियो 05:44 लेजर रीबॉर्न: सेंट को रिपोर्ट 06:24 को-ऑप एनीथिंग 07:09 स्केट 3 × मॉडर्न वॉरफेयर 2 × माइनक्राफ्ट 08:04 उपकरण क्या साबित नहीं कर सकते 08:44 REA या LeanREA इंस्टॉल करें 10:04 हमें आगे क्या रिवर्स करना चाहिए? प्रोजेक्ट और स्रोत REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA बेंचमार्क: github.com/aicodeking/leanrea/blob/main/bench/BEN… Chocolate Doom/Terraria डेमो: youtube.com Touhou 4 केस स्टडी: morluto.github.io DX-Ball केस स्टडी: morluto.github.io DX-Ball प्रोजेक्ट: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything स्केट × MW2 मैशअप: chasmlol/2010-rust-rewrite-mashup मैशअप लेखक का फुटेज: x.com फोटोक्राफ्ट क्लीन-रूम प्रोजेक्ट: storytold/photocraft संगीत: केविन मैकलेओड द्वारा "टेक लाइव" (incompetech.com), CC BY 4.0। लाइसेंस: creativecommons.org अधिक ओपन-सोर्स प्रोजेक्ट की विस्तृत जानकारी के लिए RepoSignal को सब्सक्राइब करें। [id] REA vs LeanREA: Rekayasa Balik AI dalam Game Nyata REA memberikan agen AI alat untuk memeriksa biner dan melacak bukti. LeanREA mengambil pendekatan alat shell yang lebih ringan. Kami membandingkan benchmark yang dilaporkan oleh penulis dan mengikuti proyek nyata—dari demo Doom dan Terraria hingga Touhou 4, DX-Ball, Ledger Reborn, mod co-op, dan gabungan Skate 3 × Modern Warfare 2. Waktu Doom/Terraria dan benchmark LeanREA dilaporkan oleh penulis; kami tidak menjalankannya ulang. Gabungan Skate × MW2 adalah proyek rekayasa balik yang berdekatan; penulisnya tidak mengklaim menggunakan REA. Gameplay Touhou di sini bersifat ilustratif, bukan tangkapan kasus REA. Pengujian Terraria dengan REA mencapai batas metadata dan beralih ke ILSpy. BAB 00:00 Hook dan gabungan game buatan penulis 00:47 Apa itu REA 01:22 Siklus bukti 01:57 LeanREA vs REA: tolok ukur 36 kali percobaan 03:13 Demo Chocolate Doom dan Terraria 03:48 Touhou 4: membidik lingkaran peluru 04:43 DX-Ball: posisi layar ke stereo 05:44 Ledger Reborn: laporan ke sen 06:24 Kooperatif Apa Saja 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Apa yang tidak dapat dibuktikan oleh alat 08:44 Instal REA atau LeanREA 10:04 Apa yang harus kita balikkan selanjutnya? PROYEK & SUMBER REA: morluto/rea LeanREA: aicodeking/leanrea Benchmark LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… Demo Chocolate Doom/Terraria: youtube.com Studi kasus Touhou 4: morluto.github.io Studi kasus DX-Ball: morluto.github.io Proyek DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Skate × Mashup MW2: chasmlol/2010-rust-rewrite-mashup Rekaman video penulis mashup: x.com Proyek ruang bersih PhotoCraft: storytold/photocraft Musik: “Tech Live” oleh Kevin MacLeod (incompetech.com), CC BY 4.0. Lisensi: creativecommons.org Berlangganan RepoSignal untuk lebih banyak ulasan mendalam proyek open-source. [it] REA vs LeanREA: Reverse Engineering tramite IA nei giochi reali REA fornisce a un agente IA strumenti per ispezionare file binari e tracciare prove. LeanREA adotta un approccio più leggero, basato su shelltool. Confrontiamo i benchmark dichiarati dagli autori con progetti reali, dalle demo di Doom e Terraria a Touhou 4, DX-Ball, Ledger Reborn, mod cooperative e un mashup tra Skate 3 e Modern Warfare 2. I tempi di Doom/Terraria e il benchmark di LeanREA sono dichiarati dagli autori; non li abbiamo rieseguiti. Il mashup Skate × MW2 è un progetto di reverse engineering correlato; i suoi autori non affermano di aver utilizzato REA. Il gameplay di Touhou mostrato qui è a scopo illustrativo e non rappresenta l'acquisizione del caso da parte di REA. L'esecuzione di REA su Terraria ha raggiunto il limite di metadati ed è passata a ILSpy. CAPITOLI 00:00 Hook e mashup di giochi creati dall'autore 00:47 Cos'è REA 01:22 Il ciclo delle prove 01:57 LeanREA vs REA: benchmark di 36 run 03:13 Demo di Chocolate Doom e Terraria 03:48 Touhou 4: mirare all'anello dei proiettili 04:43 DX-Ball: dalla posizione dello schermo allo stereo 05:44 Ledger Reborn: report al centesimo 06:24 Co-op Anything 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Cosa non possono dimostrare gli strumenti 08:44 Installare REA o LeanREA 10:04 Cosa dovremmo invertire ora? PROGETTI E FONTI REA: morluto/rea LeanREA: aicodeking/leanrea Benchmark di LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… Demo di Chocolate Doom/Terraria: youtube.com Caso di studio Touhou 4: morluto.github.io Caso di studio DX-Ball: morluto.github.io Progetto DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: Italiano: cranebeaker/coop-anything Mashup Skate × MW2: chasmlol/2010-rust-rewrite-mashup Filmato dell'autore del mashup: x.com Progetto PhotoCraft in camera bianca: storytold/photocraft Musica: "Tech Live" di Kevin MacLeod (incompetech.com), CC BY 4.0. Licenza: creativecommons.org Iscriviti a RepoSignal per ulteriori approfondimenti su progetti open source. [iw] REA נגד LeanREA: הנדסה לאחור באמצעות בינה מלאכותית במשחקים אמיתיים REA מספקת לסוכן בינה מלאכותית כלים לבדיקת קבצים בינאריים ומעקב אחר ראיות. LeanREA נוקטת בגישה קלה יותר של כלי מעטפת. אנו משווים את מדדי הביצועים שלהם שדווחו על ידי המחבר ועוקבים אחר פרויקטים אמיתיים - מדמואים של Doom ו-Terraria ועד Touhou 4, DX-Ball, Ledger Reborn, מודים שיתופיים ומיזוג של Skate 3 × Modern Warfare 2. התזמונים של Doom/Terraria ומדד הביצועים של LeanREA דווחו על ידי המחבר; לא הרצנו אותם מחדש. המיזוג של Skate × MW2 הוא פרויקט הנדסה הפוכה סמוך; מחבריו אינם טוענים שהוא השתמש ב-REA. משחקיות Touhou כאן היא להמחשה, לא לכידת מקרה REA. ריצת Terraria REA הגיעה למגבלת מטא-דאטה ועברה ל-ILSpy. פרקים 00:00 שילוב של Hook ומשחקים פרי יצירתו של מחבר 00:47 מהו REA? 01:22 לולאת הראיות 01:57 LeanREA נגד REA: מדד ביצועים של 36 ריצות 03:13 הדגמות של Chocolate Doom ו-Terria 03:48 Touhou 4: כוון את טבעת הכדור 04:43 DX-Ball: מיקום המסך לסטריאו 05:44 Ledger Reborn: מדווח למרכז 06:24 משחק שיתופי של כל דבר 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 מה הכלים לא יכולים להוכיח 08:44 התקנת REA או LeanREA 10:04 מה עלינו להפוך הלאה? פרויקטים ומקורות REA: morluto/rea LeanREA: aicodeking/leanrea מבחן LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… הדגמה של Chocolate Doom/Terraria: youtube.com מקרה בוחן של Touhou 4: morluto.github.io מקרה בוחן של DX-Ball: morluto.github.io פרויקט DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Skate × שילוב של MW2: chasmlol/2010-rust-rewrite-mashup קטעי וידאו של מחבר השילוב: x.com פרויקט חדר נקי של PhotoCraft: storytold/photocraft מוזיקה: "Tech Live" מאת קווין מקלאוד (incompetech.com), CC BY 4.0. רישיון: creativecommons.org הירשמו ל-RepoSignal לקבלת מידע מעמיק יותר על פרויקטים בקוד פתוח. [ja] REA vs LeanREA:実際のゲームにおけるAIリバースエンジニアリング REAは、AIエージェントにバイナリを検査し、証拠を追跡するためのツールを提供します。LeanREAは、より軽量なシェルツールアプローチを採用しています。私たちは、開発者が報告したベンチマーク結果を比較し、DoomやTerrariaのデモから東方Project 4、DX-Ball、Ledger Reborn、協力プレイMOD、そしてSkate 3とModern Warfare 2のマッシュアップまで、実際のプロジェクトを追跡しました。 Doom/Terrariaの実行時間とLeanREAのベンチマーク結果は開発者による報告値であり、私たちは再実行していません。Skate × MW2のマッシュアップは、近隣のリバースエンジニアリングプロジェクトであり、開発者はREAを使用したとは主張していません。東方Projectのゲームプレイは、REAの事例キャプチャではなく、あくまで例示です。TerrariaのREA実行はメタデータの制限に達したため、ILSpyに切り替えました。 チャプター 00:00 フックと作者作成ゲームのマッシュアップ 00:47 REAとは何か 01:22 証拠ループ 01:57 LeanREA vs REA:36回実行ベンチマーク 03:13 Chocolate DoomとTerrariaのデモ 03:48 東方Project 4:弾道リングを狙う 04:43 DXボール:画面位置をステレオ表示に 05:44 Ledger Reborn:セント単位のレポート 06:24 協力プレイゲーム 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 ツールでは証明できないこと 08:44 REAまたはLeanREAをインストールする 10:04 次に何をリバースすべきか? プロジェクトと情報源 REA: morluto/rea LeanREA: aicodeking/leanrea LeanREAベンチマーク: github.com/aicodeking/leanrea/blob/main/bench/BEN… Chocolate Doom/Terrariaデモ: youtube.com 東方Project 4 ケーススタディ: morluto.github.io DX-Ball ケーススタディ: morluto.github.io DX-Ballプロジェクト: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn 協力プレイゲーム: cranebeaker/coop-anything Skate × MW2 マッシュアップ: chasmlol/2010-rust-rewrite-mashup マッシュアップ制作者の映像: x.com PhotoCraft クリーンルームプロジェクト: storytold/photocraft 音楽: Kevin MacLeod (incompetech.com) 作曲「Tech Live」、CC BY 4.0。ライセンス: creativecommons.org RepoSignal を購読して、より多くのオープンソースプロジェクトの詳細をご覧ください。 [ko] REA vs LeanREA: 실제 게임에 적용된 AI 리버스 엔지니어링 REA는 AI 에이전트에게 바이너리를 검사하고 증거를 추적하는 도구를 제공합니다. LeanREA는 보다 가벼운 셸 도구 방식을 사용합니다. 우리는 개발자가 보고한 벤치마크 결과와 Doom 및 Terraria 데모부터 Touhou 4, DX-Ball, Ledger Reborn, 협동 모드, Skate 3와 Modern Warfare 2를 결합한 게임까지 실제 프로젝트를 비교 분석했습니다. Doom/Terraria 데모 실행 시간과 LeanREA 벤치마크 결과는 개발자가 보고한 것이며, 우리는 다시 실행하지 않았습니다. Skate 3와 Modern Warfare 2를 결합한 게임은 다른 리버스 엔지니어링 프로젝트에서 나온 것으로, 개발자는 REA를 사용했다고 주장하지 않습니다. Touhou 게임플레이 영상은 예시일 뿐, REA를 사용한 사례 캡처 영상은 아닙니다. Terraria의 경우 REA 실행 시 메타데이터 용량 제한에 도달하여 ILSpy로 전환했습니다. 목차 00:00 흥미로운 요소와 작가가 만든 게임 믹스 00:47 REA란 무엇인가 01:22 증거 순환 01:57 LeanREA vs REA: 36회 실행 벤치마크 03:13 Chocolate Doom과 Terraria 데모 03:48 Touhou 4: 탄막 조준 04:43 DX-Ball: 화면 위치를 스테레오로 변환 05:44 Ledger Reborn: 중앙 기관에 보고 06:24 협동 플레이 게임 (무엇이든) 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 도구가 증명할 수 없는 것 08:44 REA 또는 LeanREA 설치 10:04 다음에는 무엇을 리버스 엔지니어링해야 할까요? 프로젝트 및 소스 REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA 벤치마크: github.com/aicodeking/leanrea/blob/main/bench/BEN… Chocolate Doom/Terraria 데모: youtube.com 동방 4 사례 연구: morluto.github.io DX-Ball 사례 연구: morluto.github.io DX-Ball 프로젝트: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Skate × MW2 매시업: chasmlol/2010-rust-rewrite-mashup 매시업 제작자 영상: x.com PhotoCraft 클린룸 프로젝트: storytold/photocraft 음악: Kevin MacLeod의 "Tech Live" (incompetech.com), CC BY 4.0. 라이선스: creativecommons.org 더 많은 오픈 소스 프로젝트 심층 분석을 보려면 RepoSignal을 구독하세요. [ml] REA vs LeanREA: ഗെയിമുകളിലെ AI റിവേഴ്സ് എഞ്ചിനീയറിംഗ് ബൈനറികൾ പരിശോധിക്കുന്നതിനും തെളിവുകൾ കണ്ടെത്തുന്നതിനും REA ഒരു AI ഏജന്റ് ഉപകരണങ്ങൾ നൽകുന്നു. LeanREA ഒരു ഭാരം കുറഞ്ഞ ഷെൽ-ടൂൾ സമീപനമാണ് സ്വീകരിക്കുന്നത്. ഞങ്ങൾ അവരുടെ രചയിതാവ് റിപ്പോർട്ട് ചെയ്ത ബെഞ്ച്മാർക്ക് താരതമ്യം ചെയ്യുകയും യഥാർത്ഥ പ്രോജക്ടുകൾ പിന്തുടരുകയും ചെയ്യുന്നു - ഡൂം, ടെറാരിയ ഡെമോകൾ മുതൽ Touhou 4, DX-Ball, ലെഡ്ജർ റീബോൺ, കോ-ഓപ്പ് മോഡുകൾ, ഒരു സ്കേറ്റ് 3 × മോഡേൺ വാർഫെയർ 2 മാഷപ്പ് വരെ. ഡൂം/ടെറാരിയ ടൈമിംഗുകളും LeanREA ബെഞ്ച്മാർക്കും രചയിതാവ് റിപ്പോർട്ട് ചെയ്തതാണ്; ഞങ്ങൾ അവ വീണ്ടും പ്രവർത്തിപ്പിച്ചില്ല. സ്കേറ്റ് × MW2 മാഷപ്പ് ഒരു അയൽപക്ക റിവേഴ്സ്-എഞ്ചിനീയറിംഗ് പ്രോജക്റ്റാണ്; അതിന്റെ രചയിതാക്കൾ അത് REA ഉപയോഗിച്ചതായി അവകാശപ്പെടുന്നില്ല. Touhou ഗെയിംപ്ലേ ഇവിടെ ചിത്രീകരണാത്മകമാണ്, REA കേസ് ക്യാപ്ചർ അല്ല. Terraria REA റൺ ഒരു മെറ്റാഡാറ്റ പരിധിയിലെത്തി ILSpy-യിലേക്ക് മാറി. അധ്യായങ്ങൾ 00:00 ഹുക്കും രചയിതാവും നിർമ്മിച്ച ഗെയിം മാഷപ്പും 00:47 എന്താണ് REA 01:22 തെളിവ് ലൂപ്പ് 01:57 LeanREA vs REA: 36-റൺ ബെഞ്ച്മാർക്ക് 03:13 ചോക്ലേറ്റ് ഡൂമും ടെറാരിയ ഡെമോകളും 03:48 Touhou 4: ബുള്ളറ്റ് റിംഗ് ലക്ഷ്യമിടുക 04:43 DX-ബോൾ: സ്ക്രീൻ സ്ഥാനം സ്റ്റീരിയോയിലേക്ക് 05:44 ലെഡ്ജർ റീബോൺ: സെന്ററിലേക്ക് റിപ്പോർട്ട് ചെയ്യുന്നു 06:24 കോ-ഓപ്പ് എനിതിംഗ് 07:09 സ്കേറ്റ് 3 × മോഡേൺ വാർഫെയർ 2 × മൈൻക്രാഫ്റ്റ് 08:04 ഉപകരണങ്ങൾക്ക് തെളിയിക്കാൻ കഴിയാത്തത് 08:44 REA അല്ലെങ്കിൽ LeanREA ഇൻസ്റ്റാൾ ചെയ്യുക 10:04 അടുത്തതായി നമ്മൾ എന്താണ് റിവേഴ്സ് ചെയ്യേണ്ടത്? പദ്ധതികളും ഉറവിടങ്ങളും REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA ബെഞ്ച്മാർക്ക്: github.com/aicodeking/leanrea/blob/main/bench/BEN… ചോക്ലേറ്റ് ഡൂം/ടെറാരിയ ഡെമോ: youtube.com Touhou 4 കേസ് സ്റ്റഡി: morluto.github.io DX-Ball കേസ് സ്റ്റഡി: morluto.github.io DX-Ball പ്രോജക്റ്റ്: N0zoM1z0/dx-ball ലെഡ്ജർ റീബോൺ: lxistired/ledger-reborn സഹകരണം എന്തും: cranebeaker/coop-anything സ്കേറ്റ് × MW2 മാഷപ്പ്: chasmlol/2010-rust-rewrite-mashup മാഷപ്പ് രചയിതാവിന്റെ ദൃശ്യങ്ങൾ: x.com ഫോട്ടോക്രാഫ്റ്റ് ക്ലീൻ-റൂം പ്രോജക്റ്റ്: storytold/photocraft സംഗീതം: കെവിൻ മക്ലിയോഡിന്റെ "ടെക് ലൈവ്" (incompetech.com), CC BY 4.0. ലൈസൻസ്: creativecommons.org കൂടുതൽ ഓപ്പൺ സോഴ്സ് പ്രോജക്റ്റ് ആഴത്തിലുള്ള പഠനങ്ങൾക്കായി RepoSignal-ലേക്ക് സബ്സ്ക്രൈബുചെയ്യുക. [nl-NL] REA vs LeanREA: AI Reverse Engineering in echte games REA biedt een AI-agent tools om binaire bestanden te inspecteren en bewijsmateriaal te traceren. LeanREA hanteert een lichtere shell-tool-aanpak. We vergelijken hun door de auteurs gerapporteerde benchmarkresultaten met die van echte projecten – van Doom- en Terraria-demo's tot Touhou 4, DX-Ball, Ledger Reborn, co-op-mods en een Skate 3 × Modern Warfare 2-mashup. De timings voor Doom/Terraria en de LeanREA-benchmark zijn door de auteurs gerapporteerd; we hebben ze niet opnieuw uitgevoerd. De Skate × MW2-mashup is een aangrenzend reverse-engineeringproject; de auteurs beweren niet dat ze REA hebben gebruikt. De Touhou-gameplay hier is illustratief en niet de REA-case capture. De Terraria REA-run bereikte een metadatalimiet en schakelde over naar ILSpy. HOOFDSTUKKEN 00:00 Hook en een door de auteur gemaakte game-mashup 00:47 Wat REA is 01:22 De bewijslus 01:57 LeanREA vs REA: benchmark van 36 runs 03:13 Chocolate Doom en Terraria demo's 03:48 Touhou 4: richt de kogelring 04:43 DX-Ball: schermpositie naar stereo 05:44 Ledger Reborn: rapporteert tot op de cent nauwkeurig 06:24 Co-op Anything 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Wat de tools niet kunnen bewijzen 08:44 Installeer REA of LeanREA 10:04 Wat moeten we hierna reverse-engineeren? PROJECTEN & BRONNEN REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA benchmark: github.com/aicodeking/leanrea/blob/main/bench/BEN… Chocolate Doom/Terraria demo: youtube.com Touhou 4 casestudy: morluto.github.io DX-Ball casestudy: morluto.github.io DX-Ball project: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Skate × MW2 mashup: chasmlol/2010-rust-rewrite-mashup Video van de maker van de mashup: x.com PhotoCraft cleanroom-project: storytold/photocraft Muziek: “Tech Live” van Kevin MacLeod (incompetech.com), CC BY 4.0. Licentie: creativecommons.org Abonneer je op RepoSignal voor meer diepgaande analyses van open-sourceprojecten. [pa] REA ਬਨਾਮ LeanREA: ਅਸਲ ਗੇਮਾਂ ਵਿੱਚ AI ਰਿਵਰਸ ਇੰਜੀਨੀਅਰਿੰਗ REA ਬਾਈਨਰੀਆਂ ਦਾ ਨਿਰੀਖਣ ਕਰਨ ਅਤੇ ਸਬੂਤਾਂ ਦਾ ਪਤਾ ਲਗਾਉਣ ਲਈ ਇੱਕ AI ਏਜੰਟ ਟੂਲ ਦਿੰਦਾ ਹੈ। LeanREA ਇੱਕ ਹਲਕਾ ਸ਼ੈੱਲ-ਟੂਲ ਪਹੁੰਚ ਅਪਣਾਉਂਦਾ ਹੈ। ਅਸੀਂ ਉਹਨਾਂ ਦੇ ਲੇਖਕ-ਰਿਪੋਰਟ ਕੀਤੇ ਬੈਂਚਮਾਰਕ ਦੀ ਤੁਲਨਾ ਕਰਦੇ ਹਾਂ ਅਤੇ ਅਸਲ ਪ੍ਰੋਜੈਕਟਾਂ ਦੀ ਪਾਲਣਾ ਕਰਦੇ ਹਾਂ—ਡੂਮ ਅਤੇ ਟੈਰੇਰੀਆ ਡੈਮੋ ਤੋਂ ਲੈ ਕੇ ਟੌਹੌ 4, DX-ਬਾਲ, ਲੇਜਰ ਰੀਬੋਰਨ, ਕੋ-ਓਪ ਮੋਡਸ, ਅਤੇ ਇੱਕ ਸਕੇਟ 3 × ਮਾਡਰਨ ਵਾਰਫੇਅਰ 2 ਮੈਸ਼ਅੱਪ ਤੱਕ। ਡੂਮ/ਟੇਰੇਰੀਆ ਟਾਈਮਿੰਗ ਅਤੇ ਲੀਨREA ਬੈਂਚਮਾਰਕ ਲੇਖਕ-ਰਿਪੋਰਟ ਕੀਤੇ ਗਏ ਹਨ; ਅਸੀਂ ਉਹਨਾਂ ਨੂੰ ਦੁਬਾਰਾ ਨਹੀਂ ਚਲਾਇਆ। ਸਕੇਟ × MW2 ਮੈਸ਼ਅੱਪ ਇੱਕ ਗੁਆਂਢੀ ਰਿਵਰਸ-ਇੰਜੀਨੀਅਰਿੰਗ ਪ੍ਰੋਜੈਕਟ ਹੈ; ਇਸਦੇ ਲੇਖਕ ਇਹ ਦਾਅਵਾ ਨਹੀਂ ਕਰਦੇ ਕਿ ਇਸਨੇ REA ਦੀ ਵਰਤੋਂ ਕੀਤੀ ਹੈ। ਇੱਥੇ ਟੌਹੌ ਗੇਮਪਲੇ ਦ੍ਰਿਸ਼ਟਾਂਤਕ ਹੈ, REA ਕੇਸ ਕੈਪਚਰ ਨਹੀਂ। ਟੈਰੇਰੀਆ REA ਰਨ ਇੱਕ ਮੈਟਾਡੇਟਾ ਸੀਮਾ ਤੱਕ ਪਹੁੰਚ ਗਿਆ ਅਤੇ ILSpy ਵਿੱਚ ਬਦਲ ਗਿਆ। ਅਧਿਆਇ 00:00 ਹੁੱਕ ਅਤੇ ਲੇਖਕ ਦੁਆਰਾ ਬਣਾਈ ਗਈ ਗੇਮ ਮੈਸ਼ਅੱਪ 00:47 REA ਕੀ ਹੈ 01:22 ਸਬੂਤ ਲੂਪ 01:57 LeanREA ਬਨਾਮ REA: 36-ਰਨ ਬੈਂਚਮਾਰਕ 03:13 ਚਾਕਲੇਟ ਡੂਮ ਅਤੇ ਟੈਰੇਰੀਆ ਡੈਮੋ 03:48 Touhou 4: ਬੁਲੇਟ ਰਿੰਗ ਨੂੰ ਨਿਸ਼ਾਨਾ ਬਣਾਓ 04:43 DX-ਬਾਲ: ਸਟੀਰੀਓ ਲਈ ਸਕ੍ਰੀਨ ਸਥਿਤੀ 05:44 ਲੇਜਰ ਰੀਬੋਰਨ: ਸੈਂਟਰ ਨੂੰ ਰਿਪੋਰਟ ਕਰਦਾ ਹੈ 06:24 ਕੋ-ਅਪ ਐਨੀਥਿੰਗ 07:09 ਸਕੇਟ 3 × ਮਾਡਰਨ ਵਾਰਫੇਅਰ 2 × ਮਾਇਨਕਰਾਫਟ 08:04 ਟੂਲ ਕੀ ਸਾਬਤ ਨਹੀਂ ਕਰ ਸਕਦੇ 08:44 REA ਜਾਂ LeanREA ਇੰਸਟਾਲ ਕਰੋ 10:04 ਸਾਨੂੰ ਅੱਗੇ ਕੀ ਉਲਟਾਉਣਾ ਚਾਹੀਦਾ ਹੈ? ਪ੍ਰੋਜੈਕਟ ਅਤੇ ਸਰੋਤ REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA ਬੈਂਚਮਾਰਕ: github.com/aicodeking/leanrea/blob/main/bench/BEN… Chocolate Doom/Terraria ਡੈਮੋ: youtube.com Touhou 4 ਕੇਸ ਸਟੱਡੀ: morluto.github.io DX-Ball ਕੇਸ ਸਟੱਡੀ: morluto.github.io DX-Ball ਪ੍ਰੋਜੈਕਟ: N0zoM1z0/dx-ball ਲੇਜਰ ਰੀਬੋਰਨ: lxistired/ledger-reborn ਕੋ-ਆਪ ਕੁਝ ਵੀ: cranebeaker/coop-anything Skate × MW2 ਮੈਸ਼ਅੱਪ: chasmlol/2010-rust-rewrite-mashup ਮੈਸ਼ਅੱਪ ਲੇਖਕ ਫੁਟੇਜ: x.com ਫੋਟੋਕਰਾਫਟ ਕਲੀਨ-ਰੂਮ ਪ੍ਰੋਜੈਕਟ: storytold/photocraft ਸੰਗੀਤ: ਕੇਵਿਨ ਮੈਕਲਿਓਡ (incompetech.com), CC BY 4.0 ਦੁਆਰਾ “ਟੈਕ ਲਾਈਵ”। ਲਾਇਸੈਂਸ: creativecommons.org ਹੋਰ ਓਪਨ-ਸੋਰਸ ਪ੍ਰੋਜੈਕਟ ਡੂੰਘੀ ਜਾਣਕਾਰੀ ਲਈ RepoSignal ਦੀ ਗਾਹਕੀ ਲਓ। [pl] REA kontra LeanREA: Inżynieria wsteczna AI w prawdziwych grach REA udostępnia agentowi AI narzędzia do inspekcji plików binarnych i śledzenia dowodów. LeanREA stosuje lżejsze podejście oparte na narzędziach powłoki. Porównujemy ich benchmarki zgłoszone przez autorów i śledzimy rzeczywiste projekty — od dem Dooma i Terrarii po Touhou 4, DX-Ball, Ledger Reborn, mody kooperacyjne i połączenie Skate 3 × Modern Warfare 2. Czasy reakcji Dooma i Terrarii oraz benchmark LeanREA pochodzą od autorów; nie przeprowadzaliśmy ich ponownego uruchamiania. Połączenie Skate × MW2 to pokrewny projekt inżynierii wstecznej; jego autorzy nie twierdzą, że korzystał z REA. Rozgrywka w Touhou ma charakter ilustracyjny, a nie jest przechwyceniem przypadku przez REA. Przebieg Terrarii w REA osiągnął limit metadanych i został przełączony na ILSpy. ROZDZIAŁY 00:00 Haczyk i połączenie gier stworzonych przez autora 00:47 Czym jest REA 01:22 Pętla dowodowa 01:57 LeanREA kontra REA: benchmark 36 przebiegów 03:13 Dema Chocolate Doom i Terraria 03:48 Touhou 4: wyceluj pierścień kulowy 04:43 DX-Ball: pozycja ekranu w stereo 05:44 Ledger Reborn: raporty do centa 06:24 Co-op w dowolnym trybie 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Czego narzędzia nie mogą udowodnić 08:44 Zainstaluj REA lub LeanREA 10:04 Co powinniśmy cofnąć dalej? PROJEKTY I ŹRÓDŁA REA: morluto/rea LeanREA: aicodeking/leanrea Test LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… Demo Chocolate Doom/Terraria: youtube.com Studium przypadku Touhou 4: morluto.github.io Studium przypadku DX-Ball: morluto.github.io Projekt DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op: cranebeaker/coop-anything Mashup Skate × MW2: chasmlol/2010-rust-rewrite-mashup Materiały filmowe autora mashupu: x.com Projekt „clean room” w PhotoCraft: storytold/photocraft Muzyka: „Tech Live” autorstwa Kevina MacLeoda (incompetech.com), CC BY 4.0. Licencja: creativecommons.org Subskrybuj RepoSignal, aby uzyskać więcej szczegółowych informacji o projektach open source. [pt-BR] REA vs LeanREA: Engenharia Reversa de IA em Jogos Reais O REA fornece a um agente de IA ferramentas para inspecionar binários e rastrear evidências. O LeanREA adota uma abordagem mais leve, com ferramentas de análise de arquivos. Comparamos os resultados de benchmark relatados pelos autores e acompanhamos projetos reais — desde demos de Doom e Terraria até Touhou 4, DX-Ball, Ledger Reborn, mods cooperativos e uma mistura de Skate 3 com Modern Warfare 2. Os tempos de Doom/Terraria e o benchmark do LeanREA foram relatados pelos autores; não os executamos novamente. A mistura de Skate × MW2 é um projeto de engenharia reversa relacionado; seus autores não afirmam que usaram o REA. A jogabilidade de Touhou aqui é ilustrativa, não representa a captura de caso do REA. A execução do REA em Terraria atingiu um limite de metadados e passou a usar o ILSpy. CAPÍTULOS 00:00 Hook e mashup de jogos criados pelo autor 00:47 O que é REA 01:22 O ciclo de evidências 01:57 LeanREA vs REA: benchmark de 36 execuções 03:13 Demonstrações de Chocolate Doom e Terraria 03:48 Touhou 4: mire o anel de balas 04:43 DX-Ball: posição da tela para estéreo 05:44 Ledger Reborn: relatórios para o centro 06:24 Qualquer coisa cooperativa 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 O que as ferramentas não podem provar 08:44 Instale o REA ou o LeanREA 10:04 O que devemos reverter a seguir? PROJETOS E FONTES REA: morluto/rea LeanREA: aicodeking/leanrea Benchmark do LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… Demo de Chocolate Doom/Terraria: youtube.com Estudo de caso de Touhou 4: morluto.github.io Estudo de caso do DX-Ball: morluto.github.io Projeto DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Co-op Anything: cranebeaker/coop-anything Mashup de Skate × MW2: chasmlol/2010-rust-rewrite-mashup Vídeo do autor do mashup: x.com Projeto PhotoCraft clean-room: storytold/photocraft Música: “Tech Live” de Kevin MacLeod (incompetech.com), CC BY 4.0. Licença: creativecommons.org Inscreva-se no RepoSignal para mais análises detalhadas de projetos de código aberto. [ru] REA против LeanREA: обратная разработка ИИ в реальных играх REA предоставляет агенту ИИ инструменты для проверки бинарных файлов и отслеживания улик. LeanREA использует более простой подход с помощью командной оболочки. Мы сравниваем их заявленные авторами результаты бенчмарка и отслеживаем реальные проекты — от демоверсий Doom и Terraria до Touhou 4, DX-Ball, Ledger Reborn, кооперативных модов и микса Skate 3 × Modern Warfare 2. Время выполнения Doom/Terraria и бенчмарк LeanREA предоставлены авторами; мы не проводили их повторно. Микс Skate × MW2 — это соседний проект обратного проектирования; его авторы не утверждают, что в нем использовался REA. Геймплей Touhou здесь является иллюстративным, а не результатом захвата данных REA. В Terraria при использовании REA был достигнут лимит метаданных, и система переключилась на ILSpy. РАЗДЕЛЫ 00:00 Hook и созданная автором игра-микс 00:47 Что такое REA 01:22 Цикл сбора доказательств 01:57 LeanREA против REA: тест производительности за 36 запусков 03:13 Демоверсии Chocolate Doom и Terraria 03:48 Touhou 4: прицеливание в кольцо пуль 04:43 DX-Ball: от положения экрана к стерео 05:44 Ledger Reborn: отчеты в центр 06:24 Кооперативная игра в любой игре 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Что инструменты не могут доказать 08:44 Установка REA или LeanREA 10:04 Что нам следует отменить дальше? ПРОЕКТЫ И ИСТОЧНИКИ REA: morluto/rea LeanREA: aicodeking/leanrea Бенчмарк LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… Демоверсия Chocolate Doom/Terraria: youtube.com Кейс-стади Touhou 4: morluto.github.io Кейс-стади DX-Ball: morluto.github.io Проект DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Кооперативная игра в любом случае: cranebeaker/coop-anything Мэшап Skate × MW2: chasmlol/2010-rust-rewrite-mashup Видео автора мэшапа: x.com Проект PhotoCraft для чистой комнаты: storytold/photocraft Музыка: “Tech Live” Кевина Маклеода (incompetech.com), CC BY 4.0. Лицензия: creativecommons.org Подпишитесь на RepoSignal, чтобы получать больше подробных обзоров проектов с открытым исходным кодом. [ta] REA vs LeanREA: கேம்களில் செயற்கை நுண்ணறிவு மூலம் ரிவர்ஸ் இன்ஜினியரிங் (AI Reverse Engineering) REA ஒரு AI ஏஜென்ட்டிற்கு பைனரிகளை ஆய்வு செய்யவும் ஆதாரங்களைக் கண்டறியவும் கருவிகளை வழங்குகிறது. LeanREA ஒரு இலகுவான ஷெல்-டூல் அணுகுமுறையைக் கையாளுகிறது. நாங்கள் அதன் ஆசிரியர்களால் அறிவிக்கப்பட்ட பெஞ்ச்மார்க்கை ஒப்பிட்டு, டூம் மற்றும் டெராரியா டெமோக்கள் முதல் டூஹூ 4, DX-பால், லெட்ஜர் ரீபார்ன், கோ-ஆப் மோட்ஸ் மற்றும் ஒரு ஸ்கேட் 3 × மாடர்ன் வார்ஃபேர் 2 மஷப் வரையிலான உண்மையான ப்ராஜெக்ட்களைப் பின்தொடர்கிறோம். டூம்/டெராரியா டைமிங்ஸ் மற்றும் LeanREA பெஞ்ச்மார்க் ஆகியவை ஆசிரியர்களால் அறிவிக்கப்பட்டவை; நாங்கள் அவற்றை மீண்டும் இயக்கவில்லை. ஸ்கேட் × MW2 மஷப் என்பது ஒரு அருகிலுள்ள ரிவர்ஸ்-இன்ஜினியரிங் ப்ராஜெக்ட் ஆகும்; அது REA-வைப் பயன்படுத்தியதாக அதன் ஆசிரியர்கள் உரிமை கோரவில்லை. இங்குள்ள டூஹூ கேம்ப்ளே விளக்கத்திற்காக மட்டுமே, REA கேஸ் கேப்சர் அல்ல. டெராரியா REA ரன் ஒரு மெட்டாடேட்டா வரம்பை அடைந்து ILSpy-க்கு மாறியது. அத்தியாயங்கள் 00:00 ஹூக் மற்றும் ஆசிரியர் உருவாக்கிய கேம் மஷப் 00:47 REA என்றால் என்ன 01:22 ஆதார சுழற்சி 01:57 லீன்REA vs REA: 36-ரன் பெஞ்ச்மார்க் 03:13 சாக்லேட் டூம் மற்றும் டெராரியா டெமோக்கள் 03:48 டூஹூ 4: புல்லட் ரிங்கைக் குறிவைத்தல் 04:43 DX-பால்: ஸ்கிரீன் பொசிஷனை ஸ்டீரியோவாக மாற்றுதல் 05:44 லெட்ஜர் ரீபார்ன்: அறிக்கைகளை சென்டாக மாற்றுதல் 06:24 கோ-ஆப் எனிதிங் 07:09 ஸ்கேட் 3 × மாடர்ன் வார்ஃபேர் 2 × மைன்கிராஃப்ட் 08:04 கருவிகளால் நிரூபிக்க முடியாதது எது 08:44 REA அல்லது லீன்REA-ஐ நிறுவுதல் 10:04 அடுத்து நாம் எதை ரிவர்ஸ் செய்ய வேண்டும்? திட்டங்கள் மற்றும் மூலங்கள் REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA பெஞ்ச்மார்க்: github.com/aicodeking/leanrea/blob/main/bench/BEN… சாக்லேட் டூம்/டெராரியா டெமோ: youtube.com டூஹூ 4 கேஸ் ஸ்டடி: morluto.github.io DX-பால் கேஸ் ஸ்டடி: morluto.github.io DX-பால் திட்டம்: N0zoM1z0/dx-ball லெட்ஜர் ரீபார்ன்: lxistired/ledger-reborn கோ-ஆப் எனிதிங்: cranebeaker/coop-anything ஸ்கேட் × MW2 மேஷப்: chasmlol/2010-rust-rewrite-mashup மேஷப் உருவாக்கியவரின் காணொளி: x.com ஃபோட்டோகிராஃப்ட் க்ளீன்-ரூம் ப்ராஜெக்ட்: storytold/photocraft இசை: கெவின் மேக்லியோட் (incompetech.com) வழங்கும் “டெக் லைவ்”, CC BY 4.0. உரிமம்: creativecommons.org மேலும் திறந்த மூல ப்ராஜெக்ட்கள் பற்றிய ஆழமான தகவல்களுக்கு ரெப்போசிக்னலில் (RepoSignal) சப்ஸ்கிரைப் செய்யவும். [te] REA vs LeanREA: రియల్ గేమ్స్లో AI రివర్స్ ఇంజనీరింగ్ REA ఒక AI ఏజెంట్కు బైనరీలను తనిఖీ చేయడానికి మరియు ఆధారాలను కనుగొనడానికి సాధనాలను అందిస్తుంది. LeanREA తేలికైన షెల్-టూల్ విధానాన్ని అనుసరిస్తుంది. మేము వాటి రచయితలు నివేదించిన బెంచ్మార్క్ను పోల్చి చూస్తాము మరియు డూమ్, టెర్రేరియా డెమోల నుండి టోహౌ 4, DX-బాల్, లెడ్జర్ రీబార్న్, కో-ఆప్ మోడ్లు, మరియు స్కేట్ 3 × మోడర్న్ వార్ఫేర్ 2 మాషప్ వరకు ఉన్న నిజమైన ప్రాజెక్ట్లను అనుసరిస్తాము. డూమ్/టెర్రేరియా టైమింగ్లు మరియు LeanREA బెంచ్మార్క్ రచయితలు నివేదించినవి; మేము వాటిని మళ్లీ రన్ చేయలేదు. స్కేట్ × MW2 మాషప్ అనేది సమీపంలోని ఒక రివర్స్-ఇంజనీరింగ్ ప్రాజెక్ట్; అది REAను ఉపయోగించిందని దాని రచయితలు పేర్కొనలేదు. ఇక్కడ టోహౌ గేమ్ప్లే కేవలం ఉదాహరణ కోసం మాత్రమే, REA కేస్ క్యాప్చర్ కాదు. టెర్రేరియా REA రన్ మెటాడేటా పరిమితికి చేరుకుని, ILSpyకి మారింది. అధ్యాయాలు 00:00 హుక్ మరియు రచయిత రూపొందించిన గేమ్ మాషప్ 00:47 REA అంటే ఏమిటి 01:22 ఎవిడెన్స్ లూప్ 01:57 LeanREA vs REA: 36-రన్ బెంచ్మార్క్ 03:13 చాక్లెట్ డూమ్ మరియు టెర్రేరియా డెమోలు 03:48 టోహౌ 4: బుల్లెట్ రింగ్ను గురిపెట్టండి 04:43 DX-బాల్: స్క్రీన్ పొజిషన్ను స్టీరియోకు మార్చడం 05:44 లెడ్జర్ రీబార్న్: సెంట్కు నివేదికలు 06:24 కో-ఆప్ దేన్నైనా ఆడండి 07:09 స్కేట్ 3 × మోడరన్ వార్ఫేర్ 2 × మైన్క్రాఫ్ట్ 08:04 టూల్స్ ఏమి నిరూపించలేవు 08:44 REA లేదా LeanREAను ఇన్స్టాల్ చేయండి 10:04 మనం తర్వాత దేనిని రివర్స్ చేయాలి? ప్రాజెక్ట్లు & మూలాలు REA: morluto/rea LeanREA: aicodeking/leanrea LeanREA బెంచ్మార్క్: github.com/aicodeking/leanrea/blob/main/bench/BEN… చాక్లెట్ డూమ్/టెర్రారియా డెమో: youtube.com టౌహౌ 4 కేస్ స్టడీ: morluto.github.io DX-బాల్ కేస్ స్టడీ: morluto.github.io DX-బాల్ ప్రాజెక్ట్: N0zoM1z0/dx-ball లెడ్జర్ రీబార్న్: lxistired/ledger-reborn కో-ఆప్ ఎనీథింగ్: cranebeaker/coop-anything స్కేట్ × MW2 మాషప్: chasmlol/2010-rust-rewrite-mashup మాషప్ రచయిత ఫుటేజ్: x.com ఫోటోక్రాఫ్ట్ క్లీన్-రూమ్ ప్రాజెక్ట్: storytold/photocraft సంగీతం: కెవిన్ మాక్లియోడ్ రచించిన “టెక్ లైవ్” (incompetech.com), CC BY 4.0. లైసెన్స్: creativecommons.org మరిన్ని ఓపెన్-సోర్స్ ప్రాజెక్ట్ డీప్ డైవ్ల కోసం రెపోసిగ్నల్కు సబ్స్క్రయిబ్ చేసుకోండి. [uk] REA проти LeanREA: зворотна розробка ШІ в реальних іграх REA надає агенту штучного інтелекту інструменти для перевірки бінарних файлів та відстеження доказів. LeanREA використовує легший підхід до використання оболонки та інструментів. Ми порівнюємо їхній бенчмарк, про який повідомляли автори, та слідкуємо за реальними проектами — від демоверсій Doom та Terraria до Touhou 4, DX-Ball, Ledger Reborn, кооперативних модів та мішапу Skate 3 × Modern Warfare 2. Час Doom/Terraria та бенчмарк LeanREA наведені авторами; ми не перезапускали їх. Мішап Skate × MW2 — це суміжний проект зворотного інжинірингу; його автори не стверджують, що в ньому використовувалося REA. Геймплей Touhou тут ілюстративний, а не захоплення кейсу REA. Запуск Terraria REA досяг ліміту метаданих та перейшов на ILSpy. РОЗДІЛИ 00:00 Зачіпка та авторський ігровий мэшап 00:47 Що таке REA 01:22 Цикл доказів 01:57 LeanREA проти REA: бенчмарк з 36 пробігів 03:13 Демо-версії Chocolate Doom та Terraria 03:48 Touhou 4: прицілювання кільця кулі 04:43 DX-Ball: положення екрана в стерео 05:44 Ledger Reborn: звіти до центру 06:24 Кооператив Що завгодно 07:09 Skate 3 × Modern Warfare 2 × Minecraft 08:04 Що інструменти не можуть довести 08:44 Встановлення REA або LeanREA 10:04 Що нам слід змінити далі? ПРОЄКТИ ТА ДЖЕРЕЛА REA: morluto/rea LeanREA: aicodeking/leanrea Бенчмарк LeanREA: github.com/aicodeking/leanrea/blob/main/bench/BEN… Демо Chocolate Doom/Terraria: youtube.com Кейс-стаді Touhou 4: morluto.github.io Кейс-стаді DX-Ball: morluto.github.io Проект DX-Ball: N0zoM1z0/dx-ball Ledger Reborn: lxistired/ledger-reborn Кооператив Anything: cranebeaker/coop-anything Skate × MW2 mashup: chasmlol/2010-rust-rewrite-mashup Відео автора mashup: x.com Проект PhotoCraft clean-room: storytold/photocraft Музика: “Tech Live” від Kevin MacLeod (incompetech.com), CC BY 4.0. Ліцензія: creativecommons.org Підпишіться на RepoSignal, щоб отримувати більше інформації про проекти з відкритим кодом.
Location: Delhi, India Remote: Yes (worldwide) Willing to relocate: Yes, including internationally with visa sponsorship Technologies: Go, Node.js, TypeScript, JavaScript, React, Next.js, distributed systems, Linux, PostgreSQL, Redis, Kafka, Docker, gRPC, TCP/WebSockets, concurrency, mmap, io_uring, storage engines Résumé/CV: drive.google.com Email: ashishrathour1102@gmail.com GitHub: github.com/AasheeshLikePanner Backend/infrastructure engineer with ~1 year of production experience. Previously MTS at Trelium (YC F25), building sandbox and workflow infrastructure for AI agents. Production work: - Reduced persistent workspace setup from ~70s to ~10s and sandbox recovery from 486s to 14s, preserving sessions across restarts. - Made workflow registration idempotent across retries, duplicate hooks and out-of-order deployments, cutting failures from ~90% to ~1%. - Built reconnectable multi-client agent streaming with one canonical execution per task. - Previously the first engineer at Muze, where I built the entire MVP solo in 30 days, including a Go backend handling 10k+ concurrent WebSocket connections at sub-100ms latency. Systems projects: - lsm-tree-go: Go storage engine with mmap WAL, bloom filters and compaction. Profiled to ~2M writes/sec and 5x BoltDB throughput on random writes. - vase: Lock-free Go pub/sub broker with mmap WAL. ~62x Redis throughput at 100 subscribers in my benchmark. - Engram Engine: Durable agent-memory layer using event sourcing and WASM isolation, with sub-1ms sandbox overhead. Looking for Backend Engineer, Full-Stack Engineer, Founding Engineer, Infrastructure, Platform or Distributed Systems roles. Open to startups and established companies, remote or onsite, in India or internationally. Writing: medium.com
#AIOps #Research "How Much Can Tool Calls Reveal About You? Privacy Leakage from Tool-Call Traces", Oct 2026. ]-> AI45Lab/PrivacyTrace ]-> Dataset huggingface.co ]-> cyberpocket.org // PrivacyTrace studies user-profile inference from tool-call traces, without access to user conversations
Star the repo and you get yourself on the facy rope behnamazimi/knots t.co
Pra quem não quer Port de ia o HakuX TÁ RODANDO BEM PRA CARAMBA (Mediatek g57) rfandango/hakuX
source, vllm pr 59468 and the 0.33.0 release notes. heads up, cuda 12.9 wheels are gone, 13.0 only vllm#59468
LinPad — Linux for iPad. A real Linux desktop on the iPad: native windowed desktop with tiling and workspaces, real Linux apps (Firefox, VS Code, Thunar, VLC) as native windows, ARM64 JIT, GPU via Venus/Metal, keyboard + trackpad + touch. fspecii/LinPad t.co
After years of iOS development, building my first native macOS app with Rust + GPUI has been a fun learning experience. Big thanks to gpui-rs and gpui-kit for making VT Code Desktop possible! Hope you enjoy it. Feedback and bug reports are welcome. github.com/vinhnx/VTCode/issues
Most local-first notes apps keep your notes as plain text. I made a free, open-source one that encrypts them Hi r/NoteTaking, I'm GFrancV, the developer of Notvex. A while back, I posted here about the launch of my private notes app, and I've made some changes since then that I'd like to share with you. Most local-first apps (like Obsidian) keep notes as plain markdown files. That's great for portability, but anyone with access to your disk, a backup, or a synced folder can read them, so storing sensitive information there isn't the best idea. I wanted somewhere safe for my own journal and recovery codes, so I built it. How it works Everything lives in one encrypted file on your computer. Without your password it's unreadable. No account, no cloud, and the app never connects to the internet except to check for updates, which you can turn off. No telemetry either What writing looks like - Markdown editor with live preview - Tags, pinning, sorting, multi-tag filters - Command palette to jump to any note from the keyboard - Export any note or all of them to plain .md whenever you want, so you're never locked in Honest limitations - Desktop only (Windows, macOS, Linux), no mobile yet - No sync, on purpose. You can copy the file wherever you like - Search covers titles; full-text search across encrypted notes is the next hard problem - Forget your password and your recovery phrase, and your notes are gone. That's the trade-off Free and open source (AGPL-3), with no paid tier planned. GitHub: GFrancV/notvex · Site: notvex.vercel.app My question for you: what kind of notes would you never put in a cloud app? I'm trying to figure out who actually needs this.
I am seeking to become a @solana founder And turn MUSEbook into a credit provider. In order to monetize our site.. And share that revenue with my users. themusebook/musebook-credit-provider
A couple people reached out asking how I create good synthetic data. This is one approach I use: seed files → generated tasks → code-checked answers. I’ve open-sourced the CLI for training data and evals. If you spot something to improve, send a PR. mohammed840/sythsic-data-creation t.co
@leviqiao Good call, adding exactly that: tokens and minutes since the last file change, per lane and as a column, and it feeds a new "looping" state. On the roadmap: github.com/aldefy/mission-control/blob/main/ROADM…
Bring your own AI: Claude Code, opencode or OpenRouter. Fabric mod for any server + optional Paper plugin. Nothing runs until you use it. Plugin & Mod: qore-games/foreman Docs: qore-games.github.io
#Threat_Research #WebApp_Security Inside Coruna and DarkSword Chains: From Web Lures to iOS (15-18) Exploitation zimperium.com ]-> Indicators of Compromise github.com/Zimperium/IOC/tree/master/2026-10-Coru… ]-> cyberpocket.org t.co
Location: Paris / Fontainebleau, France Remote: Yes, EU/CET (hybrid Paris ok) Willing to relocate: No Technologies: TypeScript, React, Node.js, LLM agents, MCP servers, Claude Code, Codex, Figma Plugin API, TouchDesigner, WebGL/GLSL Résumé/CV: somaticbits.com... Email: hn@somaticbits.com Creative technologist / product engineer. Two sides: AI tooling and automation for teams, and generative/immersive art. Same instinct either way - prototype fast, make the abstract real. Recent work: - elfwork (elfwork.studio, work in progress): my agent-run product studio. I set direction, agents build, every change logged with what, why, and how it was checked. First product: dernier-dpe.fr - Idea Engine (open source): start from a seed word, wander an association map, and pin the path you took into a buildable concept card. Three-model pipeline - one proposes associations, one scores and filters them for surprise and coherence, one writes the card. Svelte + Hono + SQLite, runs locally in Docker. somaticbits/idea-engine - Forward-deployed engineer at a large hospitality/marketplace company. Built automations that removed up to 6h of manual work per project. - Slides and websites generated straight from existing Figma components. Design system in, finished artifact out. - MCP server that lets an agent coach and query a calisthenics training app. Looking for full-time work where AI tooling meets creative tech. Teams building something new rather than iterating on what's there. AI & automation: davidpettersson.com Generative & immersive art: somaticbits.com
Aula F108 Pro Open Source Web And Electron based controller/driver nopickart/Aula-F108-Pro-Web-and-Electron-Based-Controller I've designed a web GUI controller/driver for the Aula F108 Pro. For Try (Only For Chromium Based Browsers): nopickart.github.io
agent-desktop — Agent Desktop gives any agent reliable computer use on the desktop. Built with Rust, it sees any app's real UI structure through OS accessibility trees and... Link: vercel-labs/agent-desktop #OpenSource #GitHub #DevTools
I built a free dashboard that tests ~100 time-lagged relationships in my Garmin, Hevy and YAZIO data (with multiple-testing correction) I wanted one place where my Garmin data (sleep, HRV, resting HR, Body Battery, readiness, activities, bouldering), my Hevy strength sets and my YAZIO food log come together, and where I can see whether training actually shows up in recovery a night or two later. So I built selftopo: Live demo with invented sample data, no login: https://sh4rkfx.github.io/selftopo/dashboard/ Code (MIT): https://github.com/sh4rkfx/selftopo How it works - A GitHub Action in your own private repo syncs Garmin, Hevy and (optionally) YAZIO once a day into plain CSV files. - The dashboard is a static page. It reads those CSVs with a read-only token that stays in your browser. There is no selftopo server and no account. - German and English; installable as an app on a phone. The analysis part, since this sub will care about it - About 100 predefined pairs, e.g. training load → HRV the next night, bedtime → strength the next day, hard sets → sleep score two nights later, over the last 180 days. - Each metric is compared with its own trailing 28-day mean, so slow drifts don't look like relationships. - Spearman rank correlation; effect sizes in real units via a Theil-Sen slope. - Benjamini-Hochberg across all pairs: "robust" means q < 0.10, "tendency" means only p < 0.05. - Pairs Garmin computes from each other (e.g. Sleep Score and Readiness) are not tested. - It's association in n=1 data, not causation. A fixed weekly schedule and sick weeks are the usual sources of misleading results, and the docs say so. There's also a weekly "what's unusual" card (values outside your usual range) and a short summary per area. Honest caveats - Garmin is read with the unofficial garminconnect library, YAZIO with its private app API. Both can break, and their terms may not allow it. Hevy uses the official API (needs Hevy Pro). - Not a medical device. - I built this with heavy help from an AI coding assistant (Claude). I made the design and method decisions and I use it daily myself. I'd love your feedback on it! preview.redd.it
Show HN: PyWolf3D, a wolfenstein3D clone written from scratch in Python
My side project just passed 100 GitHub stars: system design diagrams that tell you if the design would hold up Most architecture diagrams are just pictures. You can't ask one, "will this hold at 5k requests a second?" I built Proschi so you can. You write your system as text. It draws the diagram, plays each request step by step, and simulates load, latency, availability, and cost. Your requirements can fail, like tests: db "Orders DB" [PostgreSQL] x1 requirements { survive any node failure } With one database replica, that goes red. Change x1 to x2 , and it passes (it's important that it's just an example; you can go further and define SLAs, HA, RPS, etc.) New in the latest release: I've scaled up the proschi diagrams even further; now you can connect multiple HLDs in one. i.e., if you depend on another team, you don't have to assume which components they have internally, but you can simply connect your architecture to theirs! Also, you can check whether your new feature will affect them. Free and open source (MIT), runs in your browser. It compares designs from default numbers, so it doesn't measure your real system. proschi.app · GitHub
Causely Feature Demo: Diagnosing Failures in an Agentic App Originally posted to causely.ai by Anson McCook {% youtube bBsdISbhQiY %} An agentic app adds new places for a failure to start. The agent calls tools on an MCP server, each tool calls services, and those services call databases. When a run fails, the agent reports a schema error or a failed session. The cause can sit in a tool's response contract, in the MCP server's code, in a service, or in the infrastructure. Each layer shows a different symptom, and none of them names the cause. Causely maps the whole app automatically: infrastructure, services, the request flow between them, and the agent's activity. Every agent session is linked to the tools it called, and every tool to the service behind it. Causely builds a causal model on top of that topology and reasons from the symptoms to the root cause. We ran this on Robot Shop with an agentic shopping assistant. Each run searches the catalog, compares two robots, adds one to the cart and verifies the cart, through a real agent framework, an MCP server, and the services and databases behind it. Then we injected two failures. Both look the same from the agent's side. They start in different layers. | Fault injected | Layer | What the agent saw | Causely's diagnosis | | --- | --- | --- | --- | | search_products returns price as text | Tool contract | Every run fails (schema error) | MCP tool contract violation on search_products | | Unhandled Python exception on every request | MCP server code | Every run fails | Unhandled Python exception in shop-mcp | The contract failure is the harder one to spot, because the MCP server still reports success. Causely reached each diagnosis within a few minutes. For the tool fault, the evidence clears the agent and the infrastructure. For the server fault, it ties the exception in the server's logs to error signals on shop-mcp and failed sessions on shopping-load. The causal view traces each fault to every agent session and request path it breaks, with a probability on each link in the causal chain. In production, thousands of agents and apps call one MCP server that exposes many tools, with services, databases and infrastructure behind them. A failure can start in any of those layers. Causely connects the symptoms back to the one cause behind them. Watch the video to see both failures diagnosed in Robot Shop. To see how Causely covers AI workloads, read Observe AI Workloads. For results across agents and scenarios, see the Causely benchmark.
I made Undo Skip - undo an accidental track skip and return to the exact position Ever hit next by accident and lose your place, so I built Undo Skip When you skip forward mid-track, a small glass toast appears with the track you just left. Click Undo (or press Ctrl+Shift+Z within 30 seconds) and it takes you back to the previous track at the exact second you were at. The queue and listening context are preserved, and paused playback stays paused. Nothing happens automatically the new track keeps playing until you choose undo. GitHub: Ashishranjan980/spicetify-undo-skip
[Saints Row 3 and 4] I restored the Character Sharing functionality and the Platinum for Saints Row: The Third and Saints Row IV. Hey everyone, I’ve developed a complete, cross-platform application to restore the Character Sharing functionality for Saints Row: The Third and Saints Row IV, requested by u/lancetjades. All documentation and source code are available on my GitHub. Yes, this makes the Platinum Trophy earnable again ON A NON-JAILBROKEN PLAYSTATION 3! If you want to test it yourself, a detailed README is available on the GitHub page. Project Highlights: - User-Friendly UI: No complicated command-line setups, no Docker, no other third-party apps required. It’s a simple desktop app for Windows, Linux and macOS. - Automated Setup: The Launcher automatically handles the character uploading and downloading with just a few clicks. - Trophy Unlocks: Fully restores the ability to share and download characters from the Reborn Gallery and pop the associated trophies. - RPCS3 Support. If you care about leaderboards on PSNProfiles, CRITICAL WARNING: >This method is NOT yet approved by the PSNProfiles Rules Team. Earning the UGC trophies using this custom server right now will likely result in a flag and a ban from the PSNProfiles leaderboards. If you want to test the server, please strictly use an alternate PSN account until the staff makes an official ruling. How you can help make it official? To get this method whitelisted by the PSNProfiles CRT, we need visibility, testing, and community backing. If you want to see these platinum trophies officially obtainable again for everyone: - Advocate in this post: Leave a comment below. Discuss your test results, show your support, and help bring this to the attention of the PSNP staff. - Star the GitHub Repo: Check out the repository and leave a ⭐ to show the moderators that there is massive demand for this fix. adamstark1/SaintsRow-Reborn-PS3 linktr.ee Let's bring these games back to life together! Cheers, Adam Stark
Claude Code Stop Hook: Block Early Exit Without Loops Originally published at Unattended. A Claude Code Stop hook is a command that Claude Code runs when the main agent finishes responding. If the command prints {"decision": "block", "reason": "..."}, Claude keeps working and treats the reason as its next instruction. To make an unattended run continue until a real check passes, have the hook run your tests or look for the output file, block with a specific reason while the check fails, and stop blocking after a fixed number of retries so the run can't loop forever. Which option is right for you? The best choice is the lightest Claude Code tool that can verify your "done" condition. Start from the row that matches your situation: | Your situation | What to pick first | First page to open | Why | |---|---|---|---| | Beginner, interactive session, one task | /goal with a condition such as "npm test exits 0" | Keep Claude working toward a goal | Needs no config file. It lasts for the current session only | | Daily unattended runs (cron, CI, VPS) with a test command | A command Stop hook plus your own retry counter | Hooks reference: Stop | The check is deterministic and the same in every session | | Tight budget | Command hook, a retry cap of 2–3, and --max-budget-usd on the run | Manage costs effectively | A shell check uses no model tokens. Only the retries do | | The "done" condition needs judgment (prose quality, completeness) | A prompt-based Stop hook ("type": "prompt") | Prompt-based hooks | A model judges it, so it costs a model call each time it runs | | Subagents should check their own work | A SubagentStop hook | Hooks reference: SubagentStop | It fires when a subagent finishes. Stop doesn't fire then | If you're unsure, pick the command hook. You can test it from a terminal, and it gives the same answer every time. What is a Claude Code Stop hook and when does it run? A Claude Code Stop hook is a handler registered under the Stop event. Claude Code runs it every time the main agent ends a turn. The hooks reference says Stop "Runs when the main Claude Code agent has finished responding". It doesn't run when you interrupt, and API errors fire a separate StopFailure event instead (hooks reference). This matters for unattended work because the model decides when it is finished, and it can be wrong. A Stop hook lets a script that you control decide whether the work is actually done. The hook receives JSON on stdin. These are the fields that matter for a "keep working" hook (hooks reference): | Field | What it tells you | Use it for | |---|---|---| | session_id | A unique ID for the session | Naming a retry-counter file | | stop_hook_active | true when Claude is already continuing because a Stop hook blocked | Spotting a repeat pass | | last_assistant_message | The text of Claude's final reply | Logging and notifications. The docs recommend it over reading transcript_path | | background_tasks, session_crons | Work still in flight or scheduled | Telling "done" apart from "waiting on a background job" | | cwd, transcript_path | Working directory and transcript file | Finding project files | Some points to know before you write one: - Stop has no matcher support. It fires on every occurrence (hooks guide). In an interactive session, a hook that runs tests also runs after a one-line answer to a quick question. For example, you could have your cron wrapper export a variable such as UNATTENDED=1 and make the script exit 0 when that variable isn't set. - Stop hooks fire "whenever Claude finishes responding, not only at task completion" (hooks guide). Your check has to work at any point in the task. - A command hook has a 600-second default timeout (hooks reference). A slow test suite needs a larger timeout value. For where Stop sits among the other events, see Claude Code Hooks Lifecycle: Every Event, Explained. Claude Code Stop hook example: how do you keep working until tests pass? Run your real check and block with a specific reason until it passes. When it passes, exit 0 without a decision. The decision fields for Stop are decision ("block" prevents stopping; leave it out to allow the stop) and reason, which the docs call "Required when decision is "block"". Step 1: Register the hook Add this to .claude/settings.json in your project. Use .claude/settings.local.json if you don't want to commit it. { "hooks": { "Stop": [ { "hooks": [ { "type": "command", "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/verify-before-stop.sh", "timeout": 900 } ] } ] } } Notes: 1. There is no "matcher", because Stop doesn't support one. 2. $CLAUDE_PROJECT_DIR avoids "command not found" errors when the working directory changes (hooks guide). 3. timeout is in seconds. 900 is an example value for a slow suite. Step 2: Write the script Save the following as .claude/hooks/verify-before-stop.sh and run chmod +x .claude/hooks/verify-before-stop.sh. In this example, "done" means npm test exits 0 and output/report.md exists and isn't empty. Swap in your own checks. #!/bin/bash # Example Stop hook: block until tests pass and the report exists, max N retries. INPUT=$(cat) SESSION_ID=$(printf '%s' "$INPUT" | jq -r '.session_id') ACTIVE=$(printf '%s' "$INPUT" | jq -r '.stop_hook_active') MAX_RETRIES="${STOP_HOOK_MAX_RETRIES:-3}" STATE_DIR="${CLAUDE_PROJECT_DIR:-.}/.claude/state" mkdir -p "$STATE_DIR" COUNT_FILE="$STATE_DIR/stop-$SESSION_ID.count" LOG="$STATE_DIR/stop-hook.log" # A fresh stop (not a continuation) starts a new retry budget. [ "$ACTIVE" != "true" ] && echo 0 > "$COUNT_FILE" COUNT=$(cat "$COUNT_FILE" 2>/dev/null || echo 0) # The real check. Its output goes to a file, never to stdout. if npm test --silent >"$STATE_DIR/last-test.txt" 2>&1 && [ -s output/report.md ]; then echo "$(date -u +%FT%TZ) $SESSION_ID PASS retries=$COUNT" >>"$LOG" rm -f "$COUNT_FILE" exit 0 # no decision = Claude may stop fi # Retry budget spent: allow the stop, record the failure, warn the user. if [ "$COUNT" -ge "$MAX_RETRIES" ]; then echo "$(date -u +%FT%TZ) $SESSION_ID GAVE_UP retries=$COUNT" >>"$LOG" rm -f "$COUNT_FILE" jq -n --arg n "$COUNT" \ '{systemMessage: ("Stop hook gave up after " + $n + " retries; checks still failing.")}' exit 0 fi # Block and say exactly what is still broken. echo $((COUNT + 1)) > "$COUNT_FILE" FAILS=$(tail -n 30 "$STATE_DIR/last-test.txt") jq -n --arg fails "$FAILS" '{ decision: "block", reason: ("Not done. npm test must exit 0 and output/report.md must exist and be non-empty. Last test output:\n" + $fails) }' exit 0 systemMessage is a general JSON output field that shows a message to the user. The guide lists it as something a successful hook's JSON can surface (hooks guide). Step 3: Test it before you run it unattended Pipe sample input into the script yourself: echo '{"session_id":"test1","stop_hook_active":false}' | .claude/hooks/verify-before-stop.sh echo $? You should see one JSON object with "decision": "block" while the tests fail, nothing once they pass, and an exit code of 0 in both cases. The exit-code-2 alternative There's a shorter version. Write the reason to stderr and exit 2: echo "npm test is failing; fix it before finishing" >&2 exit 2 For Stop, exit 2 "Prevents Claude from stopping, continues the conversation", and stderr reaches Claude the same way reason does. The docs say to use one approach per hook (hooks guide). The JSON form is the better fit for unattended runs, because the same script can also return systemMessage when it gives up. How do you use stop_hook_active so a Stop hook never loops forever? In Claude Code, stop_hook_active is true when Claude is already continuing because a Stop hook blocked. Read it to tell a first stop from a repeat, and pair it with a counter to set a real cap. The guide's minimal pattern exits early when the flag is true (hooks guide): if [ "$(echo "$INPUT" | jq -r '.stop_hook_active')" = "true" ]; then exit 0 # Allow Claude to stop fi That pattern prevents loops, but it allows exactly one retry. The first stop blocks. Every later stop in that continuation arrives with stop_hook_active: true, so the hook lets it through. If tests are still red after one round of fixes, the run ends red. The counter in the script above allows up to MAX_RETRIES blocks per task turn instead. Pitfalls: - Don't key the counter on the project directory only. Parallel sessions would use up each other's retries. Keying it by session_id keeps two cron jobs in the same repo from sharing a budget. - Put state under the project and outside git. Add .claude/state/ to .gitignore, or Claude may commit your counter files. - Make "give up" visible. Exiting 0 silently on the last retry looks the same as success in a cron log. Write a marker line your wrapper can grep for. AI Agent Monitoring in Claude Code: Catch Silent Failures shows how to alert on it. - Choose a small cap. Each retry is a full extra turn with your whole context. A cap of 2–3 (an example value, not an official recommendation) is enough for tests to go green after a real fix. If the suite still fails after that, the cause usually needs a human. What is CLAUDE_CODE_STOP_HOOK_BLOCK_CAP and how do you raise the limit? CLAUDE_CODE_STOP_HOOK_BLOCK_CAP is the Claude Code environment variable that raises the built-in limit on consecutive Stop hook continuations. The default is 8. The hooks reference says that after stop hooks have continued the turn eight times in a row, "Claude Code overrides the next block and ends the turn" (hooks reference, as of November 2026). When the cap is reached, the guide describes the symptom: Claude "ends the turn with a warning that the Stop hook blocked too many consecutive times" (hooks guide). That is where the "set claude_code_stop_hook_block_cap to raise this limit" text comes from. One detail matters here: "The count of consecutive continuations resets each time Claude calls a tool." The built-in cap catches a hook that blocks while Claude only replies with text. It does not catch the common unattended case, where Claude edits files and reruns tests on each pass. Each tool call resets the count, so going by the docs' wording, a test-gated hook can keep blocking well past 8. That's why your own counter is the cap that protects your token budget. How to raise it (only if you need to) 1. First confirm the hook isn't blocking on a condition that can never pass, such as a missing file path or a test that needs network access. 2. Set the variable for the run. In a shell or cron wrapper: CLAUDE_CODE_STOP_HOOK_BLOCK_CAP=12 claude -p "..." Or in a settings file, using the env key, which Claude Code reads "no matter how claude was launched" (environment variables): { "env": { "CLAUDE_CODE_STOP_HOOK_BLOCK_CAP": "12" } } 3. Keep your script's MAX_RETRIES at or below what you're willing to pay for. The guide's condition for raising it is when your hook "legitimately needs more than eight iterations to converge". Keep the built-in cap in place on unattended runs. The additionalContext output, which sends non-error feedback, goes through "the same loop protections" as decision: "block" (hooks reference). Switching to it doesn't get around the cap. How do you fix a Claude Code Stop hook "JSON validation failed" error? In Claude Code, this error means the hook's stdout parsed as JSON but didn't match the schema for the event. The guide explains that a JSON validation message means stdout "parsed as JSON but failed schema validation", and a parse message means it "looked like a JSON object but wasn't valid JSON". Both can happen "even on exit 0" (hooks guide). Common causes in Stop hooks: | What your hook printed | Problem | Fix | |---|---|---| | {"decision": "allow"} or "approve" | Stop only documents "block" | Leave decision out, or print nothing, to allow the stop | | {"decision": "block"} with no reason | reason is required with block | Add a specific reason string | | {"hookSpecificOutput": {"permissionDecision": "deny"}} | That shape belongs to PreToolUse | Use the top-level decision/reason | | {"additionalContext": "..."} at the top level | It belongs inside hookSpecificOutput with "hookEventName": "Stop" | Nest it. Fields at the top level are silently ignored (hooks guide) | | {"reason": "Line 1\nfailed "quote""} built with echo | Unescaped quotes or newlines cause a parse error | Build it with jq -n --arg. The guide recommends a JSON encoder "instead of string concatenation" (hooks guide) | A related failure produces no error at all: the decision is simply ignored. The rule is "Print nothing but the JSON object to stdout." Output that doesn't start with { is read as plain text, and the usual cause is an echo in ~/.zshrc or ~/.bashrc. The guide's fix is to wrap profile echoes in if [[ $- == *i* ]]; then ... fi so they run only in interactive shells (hooks guide). Steps to fix: 1. Start Claude Code with claude --debug-file /tmp/claude.log, then trigger a stop. 2. In the log, search for Hook output does not start with { (extra output) or Hook JSON output had unrecognized keys (fields at the wrong level). Both strings come from the hooks guide. 3. Send all debug prints to stderr (>&2) or a log file, and redirect test output to a file as the example script does. 4. Run the script by hand and pipe its output through jq .. If jq can't parse it, Claude Code can't either. Claude Code Stop hook not working: what should you check? When a Claude Code Stop hook doesn't fire or doesn't block, the usual causes are registration, the path, permissions, or stdout. Work through this table from top to bottom: | Check | How | Typical fix | |---|---|---| | 1. Is it loaded? | Type /hooks. It opens "a read-only browser for your configured hooks" | Fix the JSON (no trailing commas or comments) and the file location | | 2. Correct key? | It must be under "Stop" (case-sensitive), inside a "hooks" array | Copy the registration block above | | 3. Executable? | ls -l .claude/hooks/ | chmod +x the script | | 4. Right path? | Look for "command not found" in the transcript | Use "$CLAUDE_PROJECT_DIR"/... or an absolute path | | 5. Clean stdout? | Pipe sample JSON in by hand | Move logs to stderr and silence profile echoes | | 6. Dependencies? | Look for jq: command not found | Install jq or rewrite the script in Python | | 7. Managed policy? | /hooks shows Only hooks from managed settings run here | Your organization set allowManagedHooksOnly. Ask an admin (hooks guide) | Two Stop-specific traps: - Exit 1 doesn't block. Exit codes other than 0 and 2 without valid JSON are treated as non-blocking errors on most events (hooks guide), so exit 1 on failing tests lets Claude stop. - A broken exit-2 hook can trap Claude. On Stop, exit 2 "sends Claude back to keep working, and Claude can't repair a hook that won't run" (hooks reference). The reference treats one case as non-blocking: an exit 2 with empty stdout and a missing-file message such as No such file or directory on stderr. Other crashes still block. This is another reason to prefer the JSON form, where a crashed script doesn't print "decision": "block". To see what the hook did, press Ctrl+O to open the transcript view. A block shows the reason, and a non-blocking error shows a <hook name> hook error notice (hooks guide). If Claude Code stops mid-run for reasons unrelated to hooks, see Why Claude Code Stops Mid-Automation (and How to Fix It). Stop vs SubagentStop: which one covers subagents? In Claude Code, Stop covers the main agent and SubagentStop covers subagents. The hooks guide lists SubagentStop as firing "When a subagent finishes" (hooks guide). A Stop hook alone won't check subagent output. | | Stop | SubagentStop | |---|---|---| | Fires when | The main agent finishes a turn | A subagent finishes | | Matcher | None, always fires | Agent type, e.g. Explore or a custom agent name | | Extra input | stop_hook_active, last_assistant_message, background_tasks, session_crons | stop_hook_active, agent_id, agent_type, agent_transcript_path, last_assistant_message | | Block effect | Claude keeps working | "keeps the subagent running and delivers the reason to it as its next instruction" (hooks reference) | SubagentStop uses the same decision format as Stop. The counter script works with one change: key the counter on agent_id instead of session_id, because one session can run many subagents. { "hooks": { "SubagentStop": [ { "matcher": "test-writer", "hooks": [ { "type": "command", "command": "\"$CLAUDE_PROJECT_DIR\"/.claude/hooks/verify-subagent.sh" } ] } ] } } Pitfall: internal agents, such as prompt suggestions and /btw side questions, also trigger SubagentStop, sometimes with an empty agent_type (hooks reference). Always set a matcher with your agent's name. To choose the agent's tools, see Claude Code Subagent allowed-tools: Syntax, Examples, Fixes. How do you disable a Claude Code hook quickly? To turn off all Claude Code hooks without deleting them, set "disableAllHooks": true in a settings file. To turn off a single hook, remove its entry from the file that defines it. 1. Find which file defines it. /hooks lists configured hooks by event. Hooks can live in ~/.claude/settings.json (all projects), .claude/settings.json (project, committed), .claude/settings.local.json (project, not shared), managed policy, plugins, skills, or subagent frontmatter (hooks guide). 2. Turn off one hook. Delete its object from the "Stop" array. JSON settings don't allow comments, so you can't comment it out. 3. Turn everything off. Add "disableAllHooks": true. Precedence rules apply, so "a project's settings file can override yours", and managed hooks keep running unless the setting is also set in managed settings (hooks guide). This also turns off /goal, which runs on the hooks system (goal docs). 4. Stop a run that's already looping. Interrupt the session. Stop hooks don't run when you interrupt (hooks reference). Fix the script, then restart. Settings edits are normally picked up while Claude Code is running. If a change doesn't appear after a few seconds, restart the session (hooks guide). How do you watch token usage from Stop hook retries? Use Claude Code's /usage command in a session, cap spend on headless runs, and count blocks in your hook's log. Every block starts another turn, and that turn re-sends your whole context. 1. Inside a session, run /usage. Its Session block shows total cost and usage by model. The docs call the dollar figure "an estimate" and point API users to the Console Usage page for real billing (costs). On Pro, Max, Ultra, Team, and Enterprise plans, the same screen shows plan usage bars and a usage breakdown. 2. For headless runs, add --max-budget-usd as a hard ceiling. The costs page says session cost counts toward it (costs; flags in the CLI reference). 3. From your hook log, count retries per run: grep -c GAVE_UP .claude/state/stop-hook.log grep PASS .claude/state/stop-hook.log | tail -n 20 If many runs pass only after 2–3 retries, your prompt or CLAUDE.md probably isn't telling Claude to run the tests before it finishes. For a sense of scale, Anthropic reports an enterprise average of "around $13 per developer per active day" (costs, as of November 2026). A hook that loops all night can push a single run well past that. To get alerted, have the hook notify you when it gives up. For example, on macOS add osascript -e 'display notification "Stop hook gave up" with title "Claude Code"' to the give-up branch, or use notify-send on a Linux desktop. On a headless server, append to a file that your cron wrapper checks. The Notification event also exists for cases where Claude Code is waiting on you, such as permission_prompt or idle_prompt (hooks guide). More on cutting usage: Claude Code: How to See Token Usage (and Reduce It). Next steps Things you can do today: 1. Copy the registration block and script above. Change the check to your real "done" condition, set STOP_HOOK_MAX_RETRIES=3, and pipe sample JSON into it until the output is a single clean JSON object. 2. Add .claude/state/ to .gitignore, and add a grep GAVE_UP line to the end of your cron wrapper so a failed run doesn't look like a success. 3. Add --max-budget-usd to your claude -p command as a second limit on spend. If you'd rather not write a script: /goal is built in and costs nothing extra to set up. Its evaluator runs on the small fast model, and the docs say evaluation tokens are "typically negligible compared to main-turn spend" (goal docs). It suits interactive sessions and one-off claude -p "/goal ..." runs. It is a poor fit if you need a deterministic check, because the evaluator "doesn't run commands or read files independently" and only judges what Claude has shown in the conversation. It also lasts for one session only. For running Claude Code itself, Anthropic's subscription plans (Pro, Max, Ultra, Team, Enterprise) are listed at claude.com (as of November 2026; check the official page). Pay-per-token API billing through the Claude Console lets you set workspace spend limits (costs). Neither one replaces a retry cap in your hook. Related guides on this site: - Claude Code Hooks Examples: 7 Copy-Paste Scripts - Claude Code Cron Job Setup: Run Automations Overnight - AI Agent Monitoring in Claude Code: Catch Silent Failures FAQ Where can I find Claude Code Stop hook examples on GitHub? Anthropic's own repository has a complete hook reference implementation, the bash command validator example. It's a PreToolUse hook, but its input parsing and exit-code handling carry over to Stop. Community discussions also exist, such as this thread in ianymu/claude-verify-before-stop, but they aren't official sources. Check any community example for a retry cap and for clean stdout before you rely on it. Why does Claude Code show "running stop hook" and how long should it take? That status means your Stop hook command is running. It lasts as long as your check takes, such as the full test suite. Command hooks time out after 600 seconds by default (hooks reference). If it seems stuck, run the script by hand to time it, and raise timeout or run a faster test subset. Can a Stop hook send me a notification when Claude finishes or gives up? Yes. A Stop hook can run any command, so add a desktop notification or a webhook call to the branch that allows the stop, and use last_assistant_message for the summary text. The docs recommend that field over reading the transcript at Stop time (hooks reference). On servers, a log line that your cron wrapper checks is more reliable than a desktop notification. Sources - Hooks reference – Claude Code Docs - Automate actions with hooks (hooks guide) – Claude Code Docs - Environment variables – Claude Code Docs - Keep Claude working toward a goal (/goal) – Claude Code Docs - Manage costs effectively – Claude Code Docs - CLI reference – Claude Code Docs - Claude pricing - anthropics/claude-code: bash_command_validator_example.py - ianymu/claude-verify-before-stop discussion --- This article was created with the help of AI. Sources are linked inline; check the official documentation for the latest details.
Transformer alternative neural architecture AND its open source (: muellerberndt/cadence
✅ 一手来源: 论文 arxiv.org RAGFlow 仓库 infiniflow/ragflow 注意:据原文,BrowseComp-Plus 每题约 300 万 token;评测子集 N=200、单次运行,结论有波动空间。
@ashpreetbedi According to this passage, I made a tool that allow user coding with @DeepSeekHarness SuperAgent within iMessage wiva-hq/superagent-imessage
対策を入れてPR出しました。 そのうち何とかしてくれるとは思いますが 非公式な実行ファイルはここで共有しておきます github.com/shun20010921/VRCFaceTracking/releases/…
I'm fine with others but no type inference is weird, is it much harder than eval or it's just rarely undecidable? somebody send a PR: github.com/bendlang/bend/blob/main/bend2/bendtt.l…
@derekmross The migration detail is worth calling out too: existing users are removed from the group, but the change needs a reboot to take effect. Easy to miss if someone just updates and keeps working. omarchy#8056
Hyperbin - 跨平台的趣味桌面提醒工具 通过给系统废纸篓添加恐怖风格的动画效果,提醒用户及时清理垃圾文件 👉 hypernuclear/hyperbin t.co
Linux(ish) without the Linux kernel source, built in 11 days. Greg Kurtzer directed a coding agent to write a from-scratch Rust kernel that boots Rocky userspace with systemd included. Experimental, but the timeline and Linux binary compatibility are impressive. gmkurtzer/ginux
If you find OXR useful, give it a ⭐ on GitHub. SoMarkAI/OXR