Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9) profile picture

When Fisherman can't go to sea, they repair nets !

Joined September 2020
Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)Photo by Ash_Crypto ( 🎱 , 🎱 ) (@Crypto_Bud9)
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Anthropic just published an engineering guide on how to build always-on agents. The biggest misconception: an always-on agent does NOT run 24/7. It sleeps almost all day, wakes up for short runs, saves state, and goes back to sleep. The 5 core pieces I distilled: 1. Event Inbox Put a database table between webhooks and your agent. Acknowledge webhooks fast, run only one active worker per user so runs never collide, and batch rapid messages together. 2. Timers Keep timers in a separate table from the inbox. Split them into one-off follow-ups and recurring schedules. A background poller drops due timers into the inbox. 3. Lean Memory + Dreaming Only store what cannot be looked up again: user instructions, user notes, past messages, and task progress. Load a small index at wakeup, not every file. Run periodic dreaming passes to clean out stale facts. 4. Unattended Permissions Never put raw API keys inside the agent sandbox — inject them through an outside proxy. Use Deferred Tool Calls to pause risky actions for approval without blocking the worker. 5. Outbox Queue outgoing replies so your agent paces notifications instead of spamming users at 3 AM. claude.com/resources/article…
76
144
17
3,119
244,827
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Use self-hosted Managed Agents for work that needs access to your code and internal systems, like fixing broken builds or triaging alerts. This private beta is only available to eligible orgs, and you can request access with your Anthropic account team. claude.com/resources/article…
18
33
9
781
158,846
Ash_Crypto ( 🎱 , 🎱 ) retweeted
A graph-powered all-in-one RAG system! Fully open-source and multimodal. Modern documents increasingly contain diverse multimodal content like text, images, tables, equations, charts, and multimedia. Naive RAG cannot handle it. RAG-Anything is a graph-driven, all-in-one multimodal document processing RAG system built on LightRAG. It supports all content modalities within a single integrated framework that is built through four stages: 1️⃣ Document parsing 2️⃣ Content understanding and analysis 3️⃣ Multimodal Knowledge Graph Index construction 4️⃣ Modality-aware retrieval Built by the team behind LightRAG! GitHub repo: github.com/HKUDS/RAG-Anythin… 👉 Over to you: What types of multimodal documents do you work with most?
9
73
1
431
20,549
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Anthropic just dropped a 13-page PDF on Agent Memory - 5 layers that cut token cost 90% and make your agent actually learn: here's the 5-layer memory architecture: layer 1 → working memory - the context window. everything the agent sees right now. when it fills up, old context dies. most agents stop here and wonder why they're broken layer 2 → episodic memory - what happened. full interaction logs with timestamps. the agent recalls that the deploy failed Tuesday at 3am because the migration script had a typo layer 3 → semantic memory - what is true. facts, entities, relationships stored as a knowledge graph. "user prefers TypeScript" lives here. doesn't expire when the session ends layer 4 → procedural memory - how to do things. the agent tried 3 approaches, one worked. that method becomes a reusable skill. next time it skips straight to what worked layer 5 → forgetting - what to delete. an agent that never forgets accumulates contradictions. old preferences override new ones. the user moved cities but the agent still recommends restaurants in the old one the result: Mem0 stores 1,800 tokens per query instead of 26,000. Snowflake added one ontology layer - 20% better accuracy, 39% fewer tool calls. memory pays for itself on day one this 13-page PDF is what separates a chatbot from an agent that actually learns don't scroll past this one ↓
114
402
15
2,149
402,635
Ash_Crypto ( 🎱 , 🎱 ) retweeted
AI agent’lar için açık kaynak Palantir yapmışlar: Semantica. Veriyi knowledge graph’e çeviriyor, agent kararlarını kaydediyor ve sonradan “bu kararı neden verdi?” sorusunun izini sürebiliyorsun. Context Graph + Decision Intelligence + provenance + deterministic reasoning. Self-hosted, MIT lisanslı. github.com/semantica-agi/sem… Yapay zeka hakkında güncel kalmak için bakigul.substack.com
31
228
8
2,156
178,075
Ash_Crypto ( 🎱 , 🎱 ) retweeted
A Harvard student just found a genius way to slash LLM API token usage by 95% - dropped a whitepaper on GitHub. The twist: the token count drops massively the moment you stop sending text and turn your codebase into a PNG image. here's the whole method, step by step: step 1 → Standard prompting gets expensive - dumping raw code into the context window burns your API budget fast. step 2 → pxpipe intercepts the data - a local script renders your text and code files into highly compressed, dense images. step 3 → The LLM reads it visually - multimodal models (like Claude 3 or Gemini) process the image tokens instead of text tokens. step 4 → Massive cost reduction - visual processing is priced significantly lower, saving up to 95% on tokens without losing reasoning quality. Bookmark and read the full method in the document below.
An ex-Google engineer just dropped a 19-minute masterclass on building AI agent systems from scratch: 00:00 – Demystifying AI agent buzzwords (Harness, Eval, RAG) 00:43 – How AI agent memory actually works 03:37 – Building an AI agent harness to control the LLM 10:52 – Loop engineering and end-loop guardrails 14:18 – LLM Ops and Evaluation (Eval) 15:56 – Tracing and diagnosing agent runs 18:16 – Building a self-evolving autonomous architecture This 19-minute watch will replace tens of hours of paid AI agent courses on the internet. Bookmark and watch the full guide below
3
8
1
48
6,449
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Anthropic just dropped a 1-hour workshop on how to actually build with AI in 2026: 00:26 - Why they stopped prompting 16:57 - The system that builds, tests, and fixes itself 25:27 - One engineer replacing a 5-person team 36:25 - Building your first loop from scratch This 1-hour watch could replace 10 AI engineering courses on the internet. Watch it today, then read the step-by-step guide on building loops below.
7
107
553
88,745
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Clearest explanations of loops I've read so far
23
296
3,298
1,107,411
Ash_Crypto ( 🎱 , 🎱 ) retweeted
When you realize Docker is just Linux inside Linux inside Linux 😂
11
73
22
493
55,190
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Hierarchical knowledge graph for AI agents github.com/iwe-org/iwe
4
45
297
14,683
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Enterprise multi-agent orchestration framework github.com/kyegomez/swarms
7
65
1
408
23,014
Ash_Crypto ( 🎱 , 🎱 ) retweeted
🚨JUST IN: 7 hours ago ANDREW NG dropped one of the MOST VALUABLE FREE AI COURSES OF 2026. Most AI agents are brilliant but forget everything. This course fixes that. I went through it. Here's why this is THE MOST IMPORTANT SKILL OF 2026.👇 🔖 Save now!
20
72
2
375
34,283
Ash_Crypto ( 🎱 , 🎱 ) retweeted
The guy who created Claude Code ( @bcherny ) just leaked how his team uses Claude. One CLAUDE.md, you drop it at the root of your project. Inside: past errors, conventions, rules -Claude reads it at every session. Boris uses this every day at Anthropic:
33
48
1
758
63,401
Ash_Crypto ( 🎱 , 🎱 ) retweeted
LLM Vs. RAG Vs. AI AGENT Vs. AGENTIC AI💯💯
2
101
1
431
21,503
Ash_Crypto ( 🎱 , 🎱 ) retweeted
🚨 Opinion: India should declare WFH for corporate employees to tackle fuel disruptions. Your thoughts?
592
918
167
13,525
601,509
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Framework for AI memory mechanisms and taxonomies github.com/BAI-LAB/Survey-on…
1
37
148
7,100
Ash_Crypto ( 🎱 , 🎱 ) retweeted
𝗔𝗜 𝗢𝗯𝘀𝗲𝗿𝘃𝗮𝗯𝗶𝗹𝗶𝘁𝘆 is a must have in your tool belt as an AI Engineer. 𝗧𝗿𝗮𝗰𝗶𝗻𝗴 sits at the core of it, why is it important? Tracing and instrumentation of software have been around for decades now. With AI systems resembling regular software even more, we are now moving the practice here as well (with a few key differences). Let’s look into the process of tracing from a perspective of a naive RAG system. 𝘍𝘦𝘸 𝘥𝘦𝘧𝘪𝘯𝘪𝘵𝘪𝘰𝘯𝘴: 𝘼) An Orchestrator in the GenAI system application is the central piece of software that orchestrates the end-to-end process. Think of apps using LangChain, LlamaIndex or Haystack. 𝘽) Trace is the end-to-end application flow from the entry point till the answer is produced, it is composed of smaller pieces called spans. 𝘾) Span is a smaller piece of the application flow that represents an atomic action like a function call or a database query. They can be sequential, or run in parallel. ℹ️ As part of span we capture general metadata like start and end time, inputs and outputs of the span. On top of this metadata we track information specific to the GenAI system elements. What might a trace look like for a naive RAG system? 𝟭. A query that has been submitted to the chat application. 𝟮. The query is embedded into a vector. ✅ Additional metadata like input token count is persisted with the span so that we can estimate the cost of the procedure. 𝟯. ANN lookup performed against the Vector DB to retrieve the most relevant context. ✅ Additional metadata about the query is persisted as part of the span together with the retrieved pieces of context and their relevance. 𝟰. A prompt is constructed from the system prompt and retrieved context. 𝟱. The prompt is passed to the LLM to construct the answer. ✅ Additional metadata about input and output token count is captured together with the span so that we can estimate the cost of the procedure. Learn all of this hands-on in my End-to-end AI Engineering bootcamp. 🎁 (15% off via this link): maven.com/swirl-ai/end-to-en… 𝘞𝘩𝘺 𝘪𝘴 𝘵𝘳𝘢𝘤𝘪𝘯𝘨 𝘰𝘧 𝘎𝘦𝘯𝘈𝘐 𝘴𝘺𝘴𝘵𝘦𝘮𝘴 𝘪𝘮𝘱𝘰𝘳𝘵𝘢𝘯𝘵? - These applications are usually complex chains, errors can happen in different steps of your application. E.g. Embedding of query is taking longer than expected or you have reached API limits of LLM provider. - Cost for calling LLM APIs will be variable depending on the length of inputs and produced outputs. You would usually trace this information and analyze it to help forecast expenses. - GenAI systems are non-deterministic and will deteriorate over time. They need to be evaluated on span level rather than input/output of the entire system so that you can tune each piece separately. - … Are you tracing your Agents? Let me know in the comments 👇
16
50
1
306
17,579
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Someone literally built a free AI university - all in one repo, covering real-world AI systems step by step Link - github.com/jamwithai/arxiv-p… Here’s what you’ll learn: Week 1 - Setup everything Docker, FastAPI, databases Beginner-friendly foundation Week 2 - Feed it real data Automatically fetch research papers Fully automated data pipeline Week 3 - Teach it to search BM25 keyword search implementation Your own Google-like search system Week 4 - Make it smarter Hybrid search enabled Understands meaning, not just keywords Week 5 - It talks back Complete RAG system Ask questions, get accurate answers Week 6 - Production ready Caching and monitoring added Runs like a real product Week 7 - Give it a brain Agentic AI with LangGraph Even works with Telegram
26
411
6
2,003
148,324
Ash_Crypto ( 🎱 , 🎱 ) retweeted
Meet dots.ocr-1.5, a new vision-language model that's changing how we extract text from images. It doesn't just read text, it understands document layouts, tables, and even formulas. This is OCR on steroids, and the community is buzzing about its potential.
5
34
1
246
10,950
Ash_Crypto ( 🎱 , 🎱 ) retweeted
🚨BREAKING: Someone just built an AI coworker that actually remembers everything you've discussed. It's called Rowboat and it builds a knowledge graph from your work and runs 100% locally. - Connects Gmail, Calendar, Drive, meeting notes - Runs 100% locally (your data never leaves your machine) - Generates PDFs, briefs, emails from your context - Plain Markdown files you can edit anytime 4.6K stars. 100% Opensource.
26
69
3
509
43,578