Video wird geladen...

Video konnte nicht geladen werden

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

This GitHub repo is gold for anyone running Claude Code/ Codex / Any coding agent at all. My usage limits almost last double since I started using this. An open source context layer that stops your agent from reading 40 files to answer one question. No API key, no... show more

Srishti

11,819 subscribers

12,998 Aufrufe • vor 1 Monat •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Boris Cherny, Head of Claude Code at Anthropic: "I do not prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops." The person who built the most used AI coding tool stopped prompting entirely. Most people using it every day are still typing one request at a time. This Github repo changes that. ↳ Seven production loop patterns with real token cost estimates ↳ CLI that scaffolds your entire loop in five minutes ↳ Starters for Grok, Claude Code, Codex, and Opencode The repo gives you the framework. My article covers the mental shift that makes it actually work.

Kanika

20,576 Aufrufe • vor 18 Tagen

$THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this$

THIS MIGHT BE THE #1 OPEN-SOURCE REPO FOR CLAUDE CODE RIGHT NOW. IT GIVES CLAUDE A MEMORY AND SLASHES YOUR TOKEN COST ON EVERY QUESTION The repo is safishamsi/graphify, a free open-source skill that turns any codebase into a knowledge graph Claude Code can read instantly. Instead of grepping through your files every session, Claude gets a map of how everything connects The problem it fixes: Every time you ask Claude Code about a big repo, it does the same thing, greps through dozens of files like a brute-force Ctrl+F, blows through your context window, and sometimes still misses the answer hiding in a file nobody searched. Claude Code has no memory of how your project is structured. Every session starts from zero What it does: It maps your entire codebase into a knowledge graph, capturing not just which files exist, but which functions depend on which, which modules are central, and which files cluster around the same concern. Claude queries the map instead of scanning files How it works, three passes: 1. Code structure, free and local. Tree-sitter parses your files and pulls out classes, functions, imports and call graphs. No LLM, no tokens, just your actual code mapped deterministically 2. Audio and video, if you have them. Transcribed locally and folded into the graph 3. Docs, papers, images. Here an LLM does semantic analysis, figuring out what each document means and where it fits. Only the meaning gets sent up, never your raw source It saves you money: Normally a question about a big repo makes Claude spawn explore agents that scan file after file, eating your context window and your token budget before you get an answer. With the graph already built, Claude queries the map instead of re-reading the codebase every time. Same answer, a fraction of the tokens. The graph only gets built once, then a hook rebuilds it after each commit for free, so you never pay that scanning cost again. The bigger the repo, the bigger the gap The best parts: it's a skill, so once installed Claude knows when to use it without you memorizing commands. It works on non-code folders too, point it at docs or notes and it can spin up an Obsidian vault How to add it to your Claude: 1. Install Claude Code if you haven't: npm install -g Paul Jankura-ai/claude-code 2. Add the skill: claude skill add safishamsi/graphify 3. Open your project folder and run /graphify . to build the graph 4. Optional, make it automatic: graphify hook install so the graph rebuilds after every commit That's it. Ask Claude about your repo and it reads the map instead of burning tokens on a file hunt Bookmark this

Yarchi

55,345 Aufrufe • vor 2 Monaten

I built a form-filling agent that anyone can use 💫 This is an extremely simple but useful (I hope) app. Upload a fillable form 📋, some context files, and chat with the agent to fill the form out automatically ✍️ 1️⃣ Yes it is a Claude Code SDK wrapper 2️⃣ It is better and faster than ChatGPT/Claude UI out of the box 3️⃣ We use LlamaParse to parse the context files, so you can have more trust that we are able to read context without hallucinations (e.g. messy scanned handwriting, drivers license photo, and more). This was one of my holiday Claude Code vibe-coding projects. Built with Opus 4.5, and also powered by Opus 4.5. Feeling the AGI 🫡 App is here: Repo is open-source:

I built a form-filling agent that anyone can use 💫 This is an extremely simple but useful (I hope) app. Upload a fillable form 📋, some context files, and chat with the agent to fill the form out automatically ✍️ 1️⃣ Yes it is a Claude Code SDK wrapper 2️⃣ It is better and faster than ChatGPT/Claude UI out of the box 3️⃣ We use LlamaParse to parse the context files, so you can have more trust that we are able to read context without hallucinations (e.g. messy scanned handwriting, drivers license photo, and more). This was one of my holiday Claude Code vibe-coding projects. Built with Opus 4.5, and also powered by Opus 4.5. Feeling the AGI 🫡 App is here: Repo is open-source:

Jerry Liu

48,375 Aufrufe • vor 7 Monaten

🚨 Claude Code costs $200/month. GitHub Copilot costs $19/month. Jack Dorsey's company built a free alternative. 35,000 GitHub stars. It's called Goose. An open source AI agent built by Block that goes beyond code suggestions. It installs, executes, edits, and tests. With any LLM you choose. Not autocomplete. Not suggestions. A full autonomous agent that takes actions on your computer. No vendor lock-in. No monthly subscription. Bring your own model. Here's what Goose does: → Works with ANY LLM. Claude, GPT, Gemini, Llama, DeepSeek, Ollama. Your choice. → Reads and understands your entire codebase → Writes, edits, and refactors code across multiple files → Runs shell commands and installs dependencies → Executes and debugs your code automatically → Extensible through MCP. Connect it to any external tool. → Desktop app, CLI, and web interface. Pick your workflow. → Written in Rust. Fast. Lightweight. No bloat. Here's the wildest part: Block is a $40 billion company. They built Cash App, Square, and TIDAL. They use Goose internally. Then they open sourced the entire thing. This isn't a side project from a random developer. This is production-grade tooling from a company that processes billions in payments. Built for their own engineers. Given to everyone. Claude Code: $200/month. Locked to Claude. GitHub Copilot: $19/month. Locked to GitHub. Cursor: $20/month. Locked to their editor. Goose: Free. Any LLM. Any editor. Any workflow. Forever. 35.3K GitHub stars. 3.3K forks. 4,078 commits. Built by Block. 100% Open Source. Apache 2.0 License.

🚨 Claude Code costs $200/month. GitHub Copilot costs $19/month. Jack Dorsey's company built a free alternative. 35,000 GitHub stars. It's called Goose. An open source AI agent built by Block that goes beyond code suggestions. It installs, executes, edits, and tests. With any LLM you choose. Not autocomplete. Not suggestions. A full autonomous agent that takes actions on your computer. No vendor lock-in. No monthly subscription. Bring your own model. Here's what Goose does: → Works with ANY LLM. Claude, GPT, Gemini, Llama, DeepSeek, Ollama. Your choice. → Reads and understands your entire codebase → Writes, edits, and refactors code across multiple files → Runs shell commands and installs dependencies → Executes and debugs your code automatically → Extensible through MCP. Connect it to any external tool. → Desktop app, CLI, and web interface. Pick your workflow. → Written in Rust. Fast. Lightweight. No bloat. Here's the wildest part: Block is a $40 billion company. They built Cash App, Square, and TIDAL. They use Goose internally. Then they open sourced the entire thing. This isn't a side project from a random developer. This is production-grade tooling from a company that processes billions in payments. Built for their own engineers. Given to everyone. Claude Code: $200/month. Locked to Claude. GitHub Copilot: $19/month. Locked to GitHub. Cursor: $20/month. Locked to their editor. Goose: Free. Any LLM. Any editor. Any workflow. Forever. 35.3K GitHub stars. 3.3K forks. 4,078 commits. Built by Block. 100% Open Source. Apache 2.0 License.

Nav Toor

393,446 Aufrufe • vor 4 Monaten

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

I just found a way to use Claude Code completely free. Claude Code is Anthropic’s terminal coding agent that usually needs a paid API key to run. But a viral GitHub project called Free Claude Code, now sitting at 37k stars, lets you skip the billing entirely. It works as a tiny proxy that sits between Claude Code and free model providers like NVIDIA NIM, OpenRouter, DeepSeek, and Gemini. Every request Claude Code would send to Anthropic gets quietly rerouted to a free model on the other side. The interface stays the same. What’s actually thinking behind it changes. Setup takes a couple of quick commands and a free API key from NVIDIA NIM or OpenRouter. Paste it into the local dashboard, pick a model, and you’re building. The catch is you’re not really using Claude anymore. But when the code ships, does the model badge matter? -- I have shared the Github Link in my free Whatsapp Community ↓

Vaibhav Sisinty

36,744 Aufrufe • vor 1 Monat

Someone paid $6,000 (!) to get OpenClaw setup. So I built a free, open-source alternative: > OpenClaw Operator It's an agent skill + AGENTS.md/CLAUDE.md file that gives Codex/Claude Code the playbooks + validation flow needed to configure your local OpenClaw install. You open your OpenClaw repo/workspace in your coding agent and say things like: - “set up a cron job” - “create a custom skill” - “fix my provider config” - “troubleshoot this install and validate it” Nothing magical. Uses context from the OpenClaw open-source repo + docs to provide an effective skill. Includes: - SKILL.md - AGENTS.md/CLAUDE.md - validation checklist - task playbooks Free and open source. Contributions welcome. Demo below. Repo in reply.

Someone paid $6,000 (!) to get OpenClaw setup. So I built a free, open-source alternative: > OpenClaw Operator It's an agent skill + AGENTS.md/CLAUDE.md file that gives Codex/Claude Code the playbooks + validation flow needed to configure your local OpenClaw install. You open your OpenClaw repo/workspace in your coding agent and say things like: - “set up a cron job” - “create a custom skill” - “fix my provider config” - “troubleshoot this install and validate it” Nothing magical. Uses context from the OpenClaw open-source repo + docs to provide an effective skill. Includes: - SKILL.md - AGENTS.md/CLAUDE.md - validation checklist - task playbooks Free and open source. Contributions welcome. Demo below. Repo in reply.

Dan McAteer

17,809 Aufrufe • vor 5 Monaten

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

THE CEO OF OBSIDIAN JUST SHIPPED THE PATCH THAT LETS CLAUDE CODE DRIVE YOUR VAULT INSTEAD OF JUST READING IT. THE REPO PASSED 12,000 STARS BEFORE THE OFFICIAL ANNOUNCEMENT WENT UP 5 SKILL.md files. 1 MIT license. 0 lines of glue code drop .claude/skills/ into any vault. Claude Code registers Markdown, Bases, Canvas, CLI, and Webclipper on next session boot from that moment Claude opens the app, writes a Base view with the correct YAML, drops nodes on a Canvas, follows wikilinks correctly, clips URLs the way a power-user would. every action is a native Obsidian operation, not a text munge three formats that used to require a plugin developer or a paid template. now they get emitted by the same agent that writes your notes no MCP server. no vector db. no plugin store. no daemon in the background three years since kepano wrote "File over app". now the file has an agent that respects it you're reading this on a device that could clone the repo into your vault's .claude/skills/ folder and have Claude Code writing your first Base by lunch

chewa.

13,367 Aufrufe • vor 18 Tagen

THIS IS THE MOST COMPLETE CLAUDE CODE SETUP I'VE EVER SEEN someone open-sourced a full agent harness for Claude Code 38 agents. 156 skills. 72 commands. all pre-configured the kind of setup you'd spend weeks building yourself what's inside: → planner - feature implementation planning → architect - system design decisions → tdd-guide - test-driven development workflow → code-reviewer - quality and security review → security-reviewer - vulnerability analysis → build-error-resolver - fixes broken builds → refactor-cleaner - dead code cleanup → doc-updater - keeps docs in sync → chief-of-staff - communication triage → + 29 more agents 156 skills covering token optimization, memory persistence, continuous learning, verification loops, parallelization, subagent orchestration it ships with AgentShield baked in a security auditor that runs vulnerability checks on every agent action before execution works on Claude Code, Cursor, OpenCode, and Codex CLI one repo, one install, configured everywhere one warning: loading 38 agents and 156 skills into your context at once will burn your usage limits in minutes pick the 3-4 you actually need and load only those free. open-source. MIT licensed like + bookmark - you'll need this

THIS IS THE MOST COMPLETE CLAUDE CODE SETUP I'VE EVER SEEN someone open-sourced a full agent harness for Claude Code 38 agents. 156 skills. 72 commands. all pre-configured the kind of setup you'd spend weeks building yourself what's inside: → planner - feature implementation planning → architect - system design decisions → tdd-guide - test-driven development workflow → code-reviewer - quality and security review → security-reviewer - vulnerability analysis → build-error-resolver - fixes broken builds → refactor-cleaner - dead code cleanup → doc-updater - keeps docs in sync → chief-of-staff - communication triage → + 29 more agents 156 skills covering token optimization, memory persistence, continuous learning, verification loops, parallelization, subagent orchestration it ships with AgentShield baked in a security auditor that runs vulnerability checks on every agent action before execution works on Claude Code, Cursor, OpenCode, and Codex CLI one repo, one install, configured everywhere one warning: loading 38 agents and 156 skills into your context at once will burn your usage limits in minutes pick the 3-4 you actually need and load only those free. open-source. MIT licensed like + bookmark - you'll need this

self.dll

19,794 Aufrufe • vor 4 Monaten

A 26-YEAR-OLD AI ENGINEER WHOSE BIRMINGHAM THESIS OUTPERFORMED GOOGLE SCHOLAR BY 50% JUST SHIPPED GRAPHIFY: ONE COMMAND TURNS ANY FOLDER INTO A CLAUDE CODE SECOND BRAIN Safi Shamsi built Graphify 48 hours after Karpathy posted his LLM wiki idea. It turns any folder, codebase, docs, PDFs, into a knowledge graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this

A 26-YEAR-OLD AI ENGINEER WHOSE BIRMINGHAM THESIS OUTPERFORMED GOOGLE SCHOLAR BY 50% JUST SHIPPED GRAPHIFY: ONE COMMAND TURNS ANY FOLDER INTO A CLAUDE CODE SECOND BRAIN Safi Shamsi built Graphify 48 hours after Karpathy posted his LLM wiki idea. It turns any folder, codebase, docs, PDFs, into a knowledge graph Claude reads instead of grepping. Up to 43x fewer tokens per query. The trick almost nobody is using yet: one flag exports the entire graph as a fully-linked Obsidian vault. Repo: /safishamsi/graphify Setup, end to end: 1. Install: uv tool install graphifyy (or pipx install graphifyy). Verify with graphify --version. 2. Install the skill in Claude Code: graphify claude install. This wires Graphify into Claude Code so you can call it as a skill. 3. Open the folder you want mapped in Claude Code. In the terminal: graphify . It extracts every concept and builds the graph in graphify-out/. 4. Export to Obsidian: graphify . --obsidian. Writes one note per concept, every relationship as a wikilink, every node linked back to its source. 5. Open the new vault in Obsidian (Manage vaults → Open folder as a vault), or drag it as a subfolder into your existing one. That's it. Your Claude Code instance now has a navigable map of the codebase that loads instantly instead of re-reading files every session. Full step-by-step build of the Claude + Obsidian second brain in the article below. Bookmark this

Yarchi

141,580 Aufrufe • vor 1 Monat

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code

Claude Code is a major (and accidental!) hit for Anthropic that surprised even its creator, Boris Cherny. Claude Code, an Agentic AI coding product that lives in the terminal. Most of the new code at Anthropic is created through it today. And in the last 5 months since it was launched publicly, Claude Code went from $0 to $400M in revenue run rate (as per The Information). 00:00 – Intro 01:15 – Did You Expect Claude Code’s Success? 04:22 – How Claude Code Works and Origins 08:05 – Command Line vs IDE: Why Start Claude Code in the Terminal? 11:31 – The Evolution of Programming: From Punch Cards to Agents 13:20 – Product Follows Model: Simple Interfaces and Fast Evolution 15:17 – Who Is Claude Code For? (Engineers, Designers, PMs & More) 17:46 – What Can Claude Code Actually Do? (Actions & Capabilities) 21:14 – Agentic Actions, Subagents, and Workflows 25:30 – Claude Code’s Awareness, Memory, and Knowledge Sharing 33:28 – Model Context Protocol (MCP) and Customization 35:30 – Safety, Human Oversight, and Enterprise Considerations 38:10 – UX/UI: Making Claude Code Useful and Enjoyable 40:44 – Pricing for Power Users and Subscription Models 43:36 – Real-World Use Cases: Debugging, Testing, and More 46:44 – How Does Claude Code Transform Onboarding? 49:36 – The Future of Coding: Agents, Teams, and Collaboration 54:11 – The AI Coding Wars: Competition & Ecosystem 57:27 – The Future of Coding as a Profession 58:41 – What’s Next for Claude Code

Matt Turck

82,161 Aufrufe • vor 1 Jahr

audit and fix your entire developer docs site in under a minute We built an AI agent with Browserbase and Cerebras that audits your entire docs site > point it at any documentation site > agent goes down the link tree > agent crawls and verifies every page, checks every link, reads every code snippet > agent also compares content to your GitHub repo > returns a full report with suggested fixes and source references The full code and tutorial for how to build this yourself is live now.

audit and fix your entire developer docs site in under a minute We built an AI agent with Browserbase and Cerebras that audits your entire docs site > point it at any documentation site > agent goes down the link tree > agent crawls and verifies every page, checks every link, reads every code snippet > agent also compares content to your GitHub repo > returns a full report with suggested fixes and source references The full code and tutorial for how to build this yourself is live now.

Sarah Chieng

26,679 Aufrufe • vor 4 Monaten

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

This is one of the coolest open-source AI agent projects I've seen in a while: 'Understand Anything' It's a plugin for Claude Code, Codex, OpenCode etc. that analyzes your codebase and turns it into a knowledge base that you can interact with. It explains the codebase to you, rather than showing you the structure. It seems like it's designed for code but I opened my Obsidian vault of podcast highlights in Claude Code, then ran /understand. The result is a knowledge graph that I can search of highlights from 888 podcast episodes and 144K lines of markdown text.

Dan McAteer

174,045 Aufrufe • vor 1 Monat

I tested a new coding assistant on 34,568 lines of code. (Cursor could not achieve what this tool did.) AI models are improving every day: - Faster inference - Longer context lengths But are AI coding assistants advancing at the same rate? Can they truly understand your entire project? I tested Augment Code on my ai-engineering repo with ~35k lines of code. Augment Code is a powerful AI Assistant built for developers working with large, evolving codebases—needing an assistant that understands the full context of their projects. In the video demo below, I asked it to: - Merge two projects. - Answer a global context question. Here’s what happened: - It understood dependencies across both projects. - It merged them intelligently—without breaking anything. - It even created a README file for the merged project. - It answered my global query instantly, pulling from the full codebase. This is the difference between AI autocomplete and an AI engineer that truly understands your repo. Augment Code is powerful because it indexes your entire repo upfront. This way, it can answer questions instantly, no matter how large your project is. Lastly, Augment Code is fully compatible with VSCode, JetBrains, Vim, Slack, and more. Try them now, I have shared a link in the next tweet! Thanks to Augment Code for showing me their powerful AI coding assistant and working with me on this post.

I tested a new coding assistant on 34,568 lines of code. (Cursor could not achieve what this tool did.) AI models are improving every day: - Faster inference - Longer context lengths But are AI coding assistants advancing at the same rate? Can they truly understand your entire project? I tested Augment Code on my ai-engineering repo with ~35k lines of code. Augment Code is a powerful AI Assistant built for developers working with large, evolving codebases—needing an assistant that understands the full context of their projects. In the video demo below, I asked it to: - Merge two projects. - Answer a global context question. Here’s what happened: - It understood dependencies across both projects. - It merged them intelligently—without breaking anything. - It even created a README file for the merged project. - It answered my global query instantly, pulling from the full codebase. This is the difference between AI autocomplete and an AI engineer that truly understands your repo. Augment Code is powerful because it indexes your entire repo upfront. This way, it can answer questions instantly, no matter how large your project is. Lastly, Augment Code is fully compatible with VSCode, JetBrains, Vim, Slack, and more. Try them now, I have shared a link in the next tweet! Thanks to Augment Code for showing me their powerful AI coding assistant and working with me on this post.

Akshay 🚀

30,856 Aufrufe • vor 1 Jahr

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Anthropic just released a talk on building headless automation with Claude Code. Presented by Sid Bidasaria, Member of Technical Staff at Anthropic live at Code with Claude on May 22, 2025 in San Francisco. Here is what the talk covers. Headless mode lets you run Claude Code without a person actively typing prompts from inside an automated script. Instead of a live session, a script calls Claude with a pre-written instruction using the -p flag. This opens the door for Claude Code to become a piece of a much larger, automated process. In plain terms: Claude Code stops being a tool you use and starts being a service that runs on its own. What this unlocks: Scheduled tasks: Run Claude Code on a cron schedule without anyone at a keyboard. Fix linting errors across an entire codebase. Automatically. Overnight. CI/CD integration: Trigger Claude Code as a step in your build process. Open a PR. Claude reviews it, flags issues, and pushes fixes before a human ever looks at it. GitHub automation: A project manager comments "Claude fix this" on a GitHub issue. Claude reads the request, finds the code, writes the fix, and opens the PR. Multi-machine workflows: One orchestrator dispatches tasks to multiple Claude Code instances running in parallel across different repos simultaneously. When you combine headless mode, hooks, and GitHub Actions, development teams can automate tasks that usually eat up significant time freeing senior engineers to focus on architectural problems while Claude handles the repetitive ones. If you use Claude Code for anything beyond single sessions this talk is worth 20 minutes of your time.

Elias

14,096 Aufrufe • vor 2 Monaten

FREE 2M tokens. Opus 4.8, GPT-5.5, and every major coding model in one API key. Plugs directly into Claude Code. Inferall gives you access to the full model stack - Opus 4.8, GPT-5.5, and every other serious coding model - through one unified API. Here's the exact setup: → go to inferall(.)ai with VPN or proxy → sign in and register with any email (Google accounts work best if you hit rate limits) → create an API key - copy the key in format ifu_xxxxxxxxxxxxxxxx → go to Billing → Add a card → Activate free tier → add your card - a card with zero balance works fine(!!) → set country to United States during checkout Done. 2,000,000 free tokens loaded. Plug into Claude Code or any agent stack: BASE_URL: API_KEY: ifu_XXXXXXXXXXXXXX Works with Claude Code, OpenCode, Hermes Agent, any OpenAI-compatible setup. Opus 4.8 available immediately. 2M tokens is enough for weeks of serious coding sessions.

FREE 2M tokens. Opus 4.8, GPT-5.5, and every major coding model in one API key. Plugs directly into Claude Code. Inferall gives you access to the full model stack - Opus 4.8, GPT-5.5, and every other serious coding model - through one unified API. Here's the exact setup: → go to inferall(.)ai with VPN or proxy → sign in and register with any email (Google accounts work best if you hit rate limits) → create an API key - copy the key in format ifu_xxxxxxxxxxxxxxxx → go to Billing → Add a card → Activate free tier → add your card - a card with zero balance works fine(!!) → set country to United States during checkout Done. 2,000,000 free tokens loaded. Plug into Claude Code or any agent stack: BASE_URL: API_KEY: ifu_XXXXXXXXXXXXXX Works with Claude Code, OpenCode, Hermes Agent, any OpenAI-compatible setup. Opus 4.8 available immediately. 2M tokens is enough for weeks of serious coding sessions.

Atenov int.

25,085 Aufrufe • vor 2 Monaten

If you're hitting Claude Code's context limit, check your terminal output before blaming your project size. Every command Claude runs dumps raw output into your context window. git status : 76% of it is noise. A failed cargo test : 155 lines becomes 3. A grep across your codebase : same story You're not running out of context because your code is too big. You're running out because the commands are bleeding you dry before you get anywhere. RTK intercepts that output, compresses it, and hands Claude a clean version instead. 60–90% fewer tokens. Same information. Runs in the background after a one-command setup. Real numbers from 2,900+ commands: average 89% compression across the board. MIT license. Free. 39k GitHub stars. rtk init -g That's it. Restart Claude Code and every command is compressed automatically.

If you're hitting Claude Code's context limit, check your terminal output before blaming your project size. Every command Claude runs dumps raw output into your context window. git status : 76% of it is noise. A failed cargo test : 155 lines becomes 3. A grep across your codebase : same story You're not running out of context because your code is too big. You're running out because the commands are bleeding you dry before you get anywhere. RTK intercepts that output, compresses it, and hands Claude a clean version instead. 60–90% fewer tokens. Same information. Runs in the background after a one-command setup. Real numbers from 2,900+ commands: average 89% compression across the board. MIT license. Free. 39k GitHub stars. rtk init -g That's it. Restart Claude Code and every command is compressed automatically.

Charlie Hills

16,680 Aufrufe • vor 3 Monaten

Using Claude Code as a general agent part 3: Getting Claude Code to Ask me clarifying questions... inline, by creating a Clarifying-Questions .md file What's in this file is how the agent should format clarifying questions before doing a specific task. Rather than coming up with ALL of the context I need to give to the agent, I state what I want at the top of the docuemnt then i tell claude to ask me clarifying questions IN THE DOCUMENT. The agent knows to format them as empty code blocks and all i need to do is fill them in then tell Claude Code to finish the task at hand. Kinda niche, but I use this for EVERYTHING now: 1. State what I want at top (Ad Scripts) 2. Type out relevant context that's in my head 3. Tell the agent to ask @ clarifying-questions 4. Quickly answer them with wispr flow in the document 5. Tell Claude to continue This would be useful for nearly every workflow.

Using Claude Code as a general agent part 3: Getting Claude Code to Ask me clarifying questions... inline, by creating a Clarifying-Questions .md file What's in this file is how the agent should format clarifying questions before doing a specific task. Rather than coming up with ALL of the context I need to give to the agent, I state what I want at the top of the docuemnt then i tell claude to ask me clarifying questions IN THE DOCUMENT. The agent knows to format them as empty code blocks and all i need to do is fill them in then tell Claude Code to finish the task at hand. Kinda niche, but I use this for EVERYTHING now: 1. State what I want at top (Ad Scripts) 2. Type out relevant context that's in my head 3. Tell the agent to ask @ clarifying-questions 4. Quickly answer them with wispr flow in the document 5. Tell Claude to continue This would be useful for nearly every workflow.

Riley Brown

27,664 Aufrufe • vor 8 Monaten

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 Aufrufe • vor 1 Monat

𝗢𝗹𝗹𝗮𝗺𝗮 + 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗷𝘂𝘀𝘁 𝗺𝗮𝗱𝗲 𝗔𝗜 𝗰𝗼𝗱𝗶𝗻𝗴 𝗳𝗿𝗲𝗲. 𝗔𝗻𝗱 𝗶𝘁 𝗿𝘂𝗻𝘀 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗹𝘆 𝗹𝗼𝗰𝗮𝗹. No subscriptions. No limits. No data leaving your machine. Claude Code used to cost $3-$15 per million tokens. Now you can run it with free open-source models on your computer. January 16th, 2026: Ollama version 0.14.0 became compatible with Anthropic's messages API. That means Claude Code now works with any Ollama model. Zero ongoing costs. Your code never leaves your computer. Here's the setup: Download Ollama. Run `ollama pull qwen3-coder`. Install Claude Code. Set two environment variables to connect them. Then run: `claude --model qwen3-coder` Give it tasks in plain English: "Write a function to process images." "Debug why my API calls are failing." It reads your files. Makes changes. Tests the code. Shows you what it did. Top models: Qwen 3-Coder for everyday tasks. GPT-OSS 20B for complex projects. This is completely legal. Explicitly supported by both tools.

𝗢𝗹𝗹𝗮𝗺𝗮 + 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗷𝘂𝘀𝘁 𝗺𝗮𝗱𝗲 𝗔𝗜 𝗰𝗼𝗱𝗶𝗻𝗴 𝗳𝗿𝗲𝗲. 𝗔𝗻𝗱 𝗶𝘁 𝗿𝘂𝗻𝘀 𝗰𝗼𝗺𝗽𝗹𝗲𝘁𝗲𝗹𝘆 𝗹𝗼𝗰𝗮𝗹. No subscriptions. No limits. No data leaving your machine. Claude Code used to cost $3-$15 per million tokens. Now you can run it with free open-source models on your computer. January 16th, 2026: Ollama version 0.14.0 became compatible with Anthropic's messages API. That means Claude Code now works with any Ollama model. Zero ongoing costs. Your code never leaves your computer. Here's the setup: Download Ollama. Run `ollama pull qwen3-coder`. Install Claude Code. Set two environment variables to connect them. Then run: `claude --model qwen3-coder` Give it tasks in plain English: "Write a function to process images." "Debug why my API calls are failing." It reads your files. Makes changes. Tests the code. Shows you what it did. Top models: Qwen 3-Coder for everyday tasks. GPT-OSS 20B for complex projects. This is completely legal. Explicitly supported by both tools.

Julian Goldie SEO

168,725 Aufrufe • vor 6 Monaten

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: Repo: Sign up to LlamaCloud:

I vibe-coded an AI agent for making presentations 🤖🖼️ - accessible to everyone and open-source! You can upload both your context files, as well as a style template (a file that captures the style of the presentation you want to create). Then you launch a prompt and watch the agent one-shot your presentation. After the presentation is generated, you can edit the text inline, chat with the agent to add/modify/delete slides, and export to Powerpoint or PDF. Built with Claude Code, powered by Claude Agent SDK + LlamaParse. Hosted on Vercel/Render. To use it, you do need to specify your LlamaCloud API key and Anthropic API key (see below). App: Repo: Sign up to LlamaCloud:

Jerry Liu

21,073 Aufrufe • vor 6 Monaten