Загрузка видео...

Не удалось загрузить видео

На главную

DeepSeek GUI just dropped and it’s exactly what power users needed. A clean, local-first desktop agent workspace for DeepSeek with: • Code Mode - real file ops, planning, reviews, approvals & project context • Write Mode - excellent Markdown editor with smart AI assistance • Kun runtime - insane...

150,064 просмотров • 4 месяцев назад •via X (Twitter)

Комментарии: 33

Фото профиля FreeColorTool
FreeColorTool4 месяцев назад

Why doesn't the official DeepSeek website mention anything about a GUI? It looks like a third-party app. Be careful, it could be malware unless DeepSeek itself confirms it.

Фото профиля Manoj
Manoj4 месяцев назад

the part that interests me: "cache-first design, high hit rates." at deepseek's pricing ($0.87/M output tokens) plus aggressive caching, the cost of running a 24/7 background agent just went from "need to justify the budget" to "costs less than your spotify subscription." the economics of always-on agents just crossed a threshold.

Фото профиля Bolegebo
Bolegebo4 месяцев назад

The most interesting part isn't the model, it's the workflow. We're moving from AI as a chatbot to AI as a workspace where coding, writing, planning, and automation happen together. If the experience is smooth and the token efficiency is as good as advertised, that's a bigger deal than most benchmark improvements.

Фото профиля Saeed Anwar
Saeed Anwar4 месяцев назад

Local-first desktop agent workspace for DeepSeek is the right call — sending every context window to a remote API adds latency, cost, and data exposure that most power users don't actually want.

Фото профиля Guy Eshel
Guy Eshel4 месяцев назад

Why does it look exactly like claude code🤔

Фото профиля Gerhard K. Heilig
Gerhard K. Heilig4 месяцев назад

@Grok - is this an official DeepSeek software?

Фото профиля Kamil Kobak
Kamil Kobak4 месяцев назад

There is no version for Linux :/

Фото профиля Yash from SAYDesign
Yash from SAYDesign4 месяцев назад

local-first, cross-platform, cache-hit rates above 85%, scheduled background agents, and it costs two cents a session. we're cooked (in the best way). the bar for "what a serious AI workspace looks like" just quietly moved and most people are still debating which cloud tool to subscribe to.

Фото профиля Cj Peterson
Cj Peterson4 месяцев назад

Is it just me or does this look exactly like Claude OS desktop app lol

Фото профиля EC Ong
EC Ong4 месяцев назад

Deepseek official website makes no mention. Is this GUI website legitimate?

Фото профиля zen
zen4 месяцев назад

It maximizes token conservation, ensuring that a single "hello" message doesn't cost you $1. This is a very clever and win-win business model.

Фото профиля Yxzlwz
Yxzlwz4 месяцев назад

I have no idea why it developed a coding harness from scratch, given that Codex and OpenCode is powerful and providing SDKs.

Фото профиля Sahil
Sahil4 месяцев назад

Codex

Фото профиля ShowTimeZ
ShowTimeZ4 месяцев назад

Where is linux

Фото профиля Rehan
Rehan4 месяцев назад

So clean and fantastic

Фото профиля virat mankali
virat mankali4 месяцев назад

Deep seek is just getting fireee 🔥

Фото профиля Aaliya
Aaliya4 месяцев назад

Useful setup for faster and more private AI work.

Фото профиля Carbon
Carbon3 месяцев назад

The approval step is underrated. Most agent frameworks just execute and hope for the best. A review gate before file ops saves so many headaches.

Фото профиля AI Mastery Guide
AI Mastery Guide4 месяцев назад

The Kun runtime cache-first design is the part I want to see benchmarked against Claude Code. Anyone actually tested this yet?

Фото профиля Kraggi
Kraggi4 месяцев назад

love seeing desktop agent workspaces take off. the thing single-agent ones still miss: running a few at once without them stepping on each other's files. been building for exactly that, each agent in its own worktree. here's the setup:

Фото профиля PENIEL
PENIEL4 месяцев назад

ish

Фото профиля Whole ?
Whole ?4 месяцев назад

🤔

Фото профиля Chungus
Chungus4 месяцев назад

Cross platform Windows and Mac only 😂

Фото профиля SourceCodeplz
SourceCodeplz4 месяцев назад

it is not official from deepseek team, watch out! could be dangerous

Фото профиля Hongyu
Hongyu4 месяцев назад

DMing you! 💬

Фото профиля Shown Alan
Shown Alan4 месяцев назад

@NexEcosystem China has released a new model, the Nex-N2-Pro, which is currently ranked number one in China. Its benchmark score exceeds GPT 5.5. You can check it out.

Фото профиля keyiii
keyiii4 месяцев назад

缺一个多模态就完美了,能够满足大部分人的使用需求

Фото профиля Luo
Luo4 месяцев назад

为什么不使用Reasonix?

Фото профиля BitcoinPleb
BitcoinPleb4 месяцев назад

Is it open source?

Фото профиля furkan
furkan4 месяцев назад

Bu tür bir arayüz, projeleri yönetmeyi çok kolaylaştırıyor. Kodlama sürecini hızlandırmak için mükemmel bir çözüm!

Фото профиля Umar Nasser
Umar Nasser4 месяцев назад

@MrAhmadAwais hey, have you compared command code harness vs deepseeks native harness (if that's what this is)

Фото профиля Avais Aziz
Avais Aziz4 месяцев назад

This looks solid. The Kun runtime's cache-first approach with Code Mode file ops and project context stands out for efficiency. Local-first on macOS/Windows is a good move for power users.

Фото профиля David27
David274 месяцев назад

where can I find this?

Похожие видео

AI Messenger: Giving Voice to Autonomous Agents The future of AI isn't just about making agents smarter - it's about making them truly autonomous. Today, we're taking a major step toward this future with AI Messenger, a breakthrough that fundamentally changes how AI agents operate, communicate, and create value. The Innovation We've developed a new way for AI agents to communicate. At its core is the 'incoming_message' workflow trigger - a system that lets any platform or user interact directly with Loomlay agents through a messaging endpoint. Direct Interaction Imagine having an AI assistant you can chat with anytime, through any platform - Telegram, your website, or custom interface. Ask "What's happening with $ETH today?" and your agent analyzes market data, checks trading volumes, and gives you a comprehensive update. Your agent maintains context, understanding exactly what you need. Event-Driven Intelligence The power of AI Messenger goes beyond direct communication: ▪️Trading agent executes when whale wallet movements exceed threshold ▪️Research agent alerts when new protocol documentation drops ▪️Analytics agent triggers when volume patterns match historical pumps ▪️Portfolio agent re-balances, when asset allocation hits specified limits This is true automation - agents that act precisely when needed. A New Era of Collaboration We're creating an ecosystem where agents work together seamlessly: ▪️Research agents feed insights to trading agents ▪️analytics agents alert management agents ▪️support agents tap into knowledge agents This isn't just automation - it's an intelligent network where each agent enhances the capabilities of others. B2B Solution Imagine a DEX, where users can ask about liquidity pools, trading pairs, or market trends through a simple chat interface - and get answers from an agent that knows your protocol inside out. Or a lending platform where users chat with an agent that understands their positions and can provide real-time advice. Implementation is seamless - we handle the agent creation and widgets setup,our partners provide the value to their users. The Future of AI Agents This update represents a fundamental shift in how AI agents operate. We're moving from isolated, scheduled tasks to an interconnected ecosystem of responsive, collaborative agents. This is our vision of truly autonomous AI - intelligent systems that communicate, collaborate, and respond to real needs in real-time. Telegram integration is available right now. Below is a sneak peak of what's coming next week 🪄 Because $LAY is the way!

Loomlay

26,149 просмотров • 1 год назад

Hermes agent just left the terminal. 𝗛𝗲𝗿𝗺𝗲𝘀 𝗗𝗲𝘀𝗸𝘁𝗼𝗽 dropped yesterday. native app for macOS, Windows, and Linux. for months Hermes was the agent that learned your projects, wrote its own skills, and built a model of who you are. all of it buried in terminal logs. now it has a window. the important part is that it's not a wrapper. it runs the same agent core, the same sessions, memory, and skills as the CLI. you can start a task in the terminal and finish it in the app without anything resetting. the state is shared across every interface, not copied between them. what the GUI actually adds: → streaming chat that shows live tool calls and inline reasoning instead of a spinner → a preview rail that renders pages, code, and images right beside the conversation → an artifacts panel that collects every file the agent has ever produced → remote gateway mode, so you can point the app at a VPS and run the heavy work elsewhere → skills, cron, profiles, and gateways managed point-and-click instead of through YAML → voice mode, drag-drop files, and inline image generation remote gateway mode is the one worth slowing down on. the agent runs 24/7 on a $5 server while you control it from your laptop like a local app. other agent UIs are chatboxes with a logo. this one shows the autonomy instead of hiding it, so you watch the skills load, the tools fire, and the artifacts pile up as it works. it was teased in Jensen's GTC keynote. MIT licensed, local-first, no telemetry. if you already run Hermes, download it and everything is already there. your chats, memory, and skills carry straight over. i wrote a full masterclass on Hermes Agent that walks through the SOUL. md identity layer, the three-tier memory system, the self-evolving skills loop, and how to run three specialized agents 24/7. desktop is the interface that finally does all of it justice. the article is quoted below.

Akshay 🚀

51,540 просмотров • 4 месяцев назад

Meet WebBrain: An Open-Source, Local-First AI Browser Agent That Reads Pages and Automates Tasks in Chrome and Firefox WebBrain lives inside your browser and can run entirely on your own local model — no cloud, no account, no data leaving your machine. Most "AI browser agents" are a chat box that pastes your page into someone else's server. That's not an agent that lives where you browse — and WebBrain draws a very clear line between the two. It's an open-source (MIT), local-first browser agent for Chrome and Firefox. It runs inside your existing authenticated session, on a model you pick — so with llama.cpp or Ollama, nothing leaves your machine. Here's what's actually interesting: → Two modes, cleanly separated. Ask reads the page (read-only, content scripts). Act clicks and types through the Chrome DevTools Protocol (chrome.debugger) — trusted input events that modern sites honor, reaching cross-origin iframes and shadow DOM. → UI-first by design. For anything that submits, sends, or buys, it drives the visible UI and refuses to hit REST/GraphQL endpoints directly. It starts read-only and asks before consequential actions. → Bring any model. llama.cpp, Ollama, LM Studio, vLLM — or OpenAI, Claude, Gemini, DeepSeek, Groq, OpenRouter. Recommended local: Qwen 3.6 35B (Qwen3.6-35B-A3B), which beat Gemma 4 on the project's screenshot benchmark. → Tuned for cost and privacy. Token-conscious screenshots, oldest-first context trimming, a dedicated vision model, 40+ tools (~20 in Compact mode). No telemetry. No accounts. Full analysis: GitHub Repo: Chrome Extension: Firefox Add-on: Portal:

Marktechpost AI

203,011 просмотров • 3 месяцев назад

I have been testing DeepSeek-V4-Pro with the Pi coding agent. I am mindblown by how well it works out of the box. A few notes: I spent a few hours building an LLM wiki with an agent powered entirely by DeepSeek-V4-Pro on Fireworks inference. This is the first time I feel like there is an open-weight model that can reason at the level of Claude and Codex. And it does this in a cost-effective way with support for 1M context length. To be clear, I am using DeepSeek-V4-Pro inside of Pi without any special configuration. It works out of the box. It's exciting that there is a model that can just be plugged into a basic harness like Pi, and it just works. I've never seen that before. Most models require lots of configuration and setup. DeepSeek's DeepSeek-V4-Pro is clearly good at agentic coding (probably the best from the open-weight models), but the model is also great on knowledge-intensive tasks where reasoning matters. The agent pulled agentic engineering best practices from different company docs (Anthropic, OpenAI, Google, Stripe, Meta, Modal, DeepSeek, Mistral, Cohere), searched and digested Reddit and HN threads, summarized arxiv papers, and surfaced trending GitHub repos. Then it distilled everything into actionable tips across categories. I love the Wiki it built. The quality is really good. Here is a snapshot of what the wiki looks like: DeepSeek-V4-Pro handled the task without breaking stride. Multi-step research queries, code generation for scaffolding, context-heavy reasoning across disparate sources. For coding specifically, this is the first open-weight model that genuinely feels like a Codex or Claude Code experience. It compares in capability and actual multi-turn agentic work. What made the loop feel so responsive was Fireworks' inference speed (the fastest in the market) and the fact that they actually validate models at the systems level before shipping. No corrupted reasoning traces. Just fast, reliable iteration. The hybrid CSA and HCA attention design cuts KV cache to just 10% and inference FLOPs by nearly 4x at 1M-token context. This is what makes the agent loop actually fast and cheap enough to run in practice. For devs who've been watching open-weight models close the gap but haven't found one that actually delivers in practice, this is the closest I've seen. Try it here:

elvis

60,281 просмотров • 5 месяцев назад

HOLY SH*T! The person who leaked this online is a real freaking madman! Now everyone can get 800 million tokens for AI agents for free The OmniRoute repository is blowing up GitHub. It is a local high-performance AI gateway that combines free limits from dozens of providers into a single continuous API stream Project architecture and key technical specifications: Interface and Integration: Provides a single OpenAI-compatible API endpoint. Natively connects to Cursor, VS Code (via Copilot / Cline / Aider) Claude Code, and custom scripts Connection Scale: Supports 350+ providers and 90+ services with free limits (Google AI Studio, Groq, Cerebras, SambaNova, OpenRouter, GitHub Models, Mistral AI, etc.) 18 Routing Strategies & Auto-Fallback: Custom switching system. On a ⁠429 Too Many Requests⁠ error or quota depletion, the gateway seamlessly redirects the request to the next model in the chain within milliseconds Dual Context Compression (RTK + Caveman): Built-in engines cut unnecessary logs, syntax, and message history by 15–95% saving token volume before sending the request Security (Local-first & 0 Telemetry): All API keys are locally encrypted using the AES-256-GCM algorithm. Data goes directly to providers, bypassing third-party clouds Agent Protocols (MCP & A2A): Full support for Model Context Protocol (MCP) and Agent-to-Agent architecture for automated model pool management Launch Options: CLI (⁠npm⁠), Docker container, Electron desktop app, and PWA

Bober_smart

20,016 просмотров • 5 дней назад

I tried jack's Buzz. It's like Slack + OpenClaw + Herdr + but with some really unique features that people are sleeping on. The video below shows how it works, and some of my thoughts on the process and platform, e.g.: - Create and interact with agents on top of any harness (claude code, codex, pi, etc.) - Choose which models agents use, including local ones - Agents can delegate work and work in parallel in git worktrees - Agents are first-class citizens and work like humans (creating channels, delegating, access to chat history) - You can share AI compute within a community - It's completely open-source and decentralized Things I like: - Delegating work in chat feels natural: tag an agent, it replies in a thread with status updates as it e.g. compiles, commits, and deploys. - Shared compute: relay owners can share local compute with members, so a community could pool funds for one beefy machine running a local model and everyone uses it. - It's built on Nostr, an open protocol already tied into Bitcoin Lightning so I can imagine communities tipping each other or paying for compute/agent tasks with instant zero-fee micropayments in the future. - It ties together things like OpenClaw, an agent manager, and Slack-style chat into one tool. Things I didn't like: - You can't see what the agent is doing in a terminal. The activity view exists, but if you're used to watching a session run, this UI feels a bit abstracted. A terminal view would be great. - It feels slower than running a session in Claude Code, though no evidence to back that up. For that reason I found myself doing one-off tasks in the terminal instead. Verdict: - I really like it so far and can genuinely imagine working with a team this way. - It doesn't feel ready for big, complex tasks yet. For shallower tasks, it's perfect. - The shared compute + Nostr/Lightning angle is what really separates it from every other agent manager for me, and I think that future is coming.

Vinny

1,360,390 просмотров • 2 месяцев назад

Introducing Workshop: cloud + on-device agentic AI. And to celebrate, we're giving away $250k in Google Gemini AI credits. (details below). The future of AI work is neither cloud-based nor local. It's both. In Workshop Cloud, you can use agents powered by frontier models like Claude and/or open source models like Z.ai's GLM-5 to build internal tools, dashboards, and AI web apps. Or, breeze through tasks like managing your Google and Meta Ads. In Workshop Desktop, you can do all the same right on your computer, plus make desktop apps, mobile apps, and 3D creations. Our favorite part? You can power the full agent experience with local models like Qwen 3.5 family on your computer. Fully offline. 2026 is the year in which local models for agentic tasks will become viable for mainstream use. But the setup for tools like OpenClaw is like setting up Linux from scratch on your computer. Workshop Desktop is one-click to install on Windows, Mac, and Linux. It recommends which open source model you should use for your hardware and lets you download and run it right in the app. And its agent harness allows you to chat, create websites, build personal utilities, and analyze data. 100% offline. Or multitask with AI models in the cloud while running other agent threads locally. Start in Workshop Cloud when you want flexibility and speed. Download your project and continue in Workshop Desktop when you want local files, privacy, and/or better performance on large code bases. Publish from either. The agent tooling space is maturing and discerning users have come to expect a lot from their tools. We've packed Workshop with features to help you 10x your productivity. - Native support for skills - Autocompaction for seamless context management - Built-in AI for your apps - Dozens of connectors, like Google Drive, Big Query, and Supabase - dbt integration to ground your dashboards in your semantic layer - Native Github integration - Private app deployment - ... and more (+ we're shipping super fast) To access the free credit offer, RT this post and reply with "Workshop". Make sure you are following us so we can DM you the instructions to redeem. - First 100 to RT + comment get $500 in credits. - Everyone else gets up to $250 And thanks to our partners Modal, Google Gemini, and Z.ai!

Workshop AI

29,606 просмотров • 6 месяцев назад

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 просмотров • 3 месяцев назад

Jev has been blowing up lately. If you've got the Jev API but don't know how to play around with it yet, you can just copy this checklist. 1. jev-ultrafast A high-speed browser Agent built with Browser Use. Jev only judges "what to do, which element to click" at each step, and only calls the small model when typing is needed. Searching for a flight on Google Flights takes about 7 seconds. 2. fast-jev-compaction Context compression for Claude Code. Before each tool call, have Jev judge if there's anything still useful; delete the useless stuff, and keep the original text without rewriting it. 3. json-render Vercel Labs' generative UI framework. In experiments, Jev doesn't write JSON token by token; it just handles selecting components, properties, and layouts. 4. typesafe-mcp Best for people who just got the API. Plug Jev into Claude Code, Claude Desktop, Codex, and Pi, and do Choice / Score / Noul anytime. 5. jev-mcp Ready-made Agent judgment toolkit: fact-checking, content screening, semantic ranking, classification, and information extraction. 6. SemDecide Turn Jev into a command-line tool. Directly classify, score, and filter in the Shell—great for hooking up to crawlers, CI, and data pipelines. 7. jev-codex-router First have Jev judge how hard this round of programming tasks is, then decide the model tier, reasoning depth, and speed mode. 8. Winnow Context garbage collection for Claude Code. When Read / Bash / Grep spits out a ton of stuff, Jev first judges which parts are really relevant to the current task. 9. jev-review Before code review, run it through Jev first to pick out high-risk changes, then hand them off to a pricier big model or a human. Comes with a local dashboard. 10. Blink Use Jev as a code repository navigator. At each directory level, judge which files are most relevant to the current issue, then keep digging down. Copy these complete Jev blueprints - then read full Jev setup below ↓ ↓

rody

204,073 просмотров • 22 дней назад

voice prompting is 4x faster than typing. but i NEEEDED more. Nvidia parakeet allows me to fully voice control an agentic development environment with commands firing in under 300ms. and it runs 100% local. I added gpt realtime 2.1 mini, its 20% faster, 7 to 20x cheaper, and lets you have full jarvis style control of your vibe coding agents. but what about orchestration? agents can spawn each other, prompt each other, and read each others output with the CNVS mcp and cli. Fable 5 can create a plan, spawn 10 grok agents to execute, and a kimi k3 agent to review. parallel agents code at 1,000s of TPS anthropic's own research shows improvements ACROSS the board for multi agent workflows over single agent but only CNVS lets you choose exactly which orchestration, worker, and reviewer agent you would like to use. grok, kimi, qwen, claude, codex... the cross agent memory system is based on real 2026 research so all agents share the same brain, its on demand so it never bloats context. what about remote agents?? You can create remote canvasses that run agents your virtual private servers, they keep working even if your mac shuts off, and you can even vibe code straight to production. CNVS is built from the ground up ENTIRELY in swift for RAW performance on apple hardware. PS - its a LIFE TIME LICENSE because you don't need another subscription. PPS - I ship updates every week based off user feedback and livestream myself building it everyday. PPPS - it uses all your existing ai subs, so no api pricing here.

Max Blade

61,082 просмотров • 2 месяцев назад

HERMES AGENT SUPPORTS 7 TYPES OF AI AGENTS. EACH ONE TAKES LESS THAN 90 SECONDS TO SET UP. MOST PEOPLE ONLY BUILD THE FIRST ONE. HERE ARE ALL SEVEN AND WHEN TO USE EACH. 1. BASIC AGENT WITH TOOLS your agent with access to terminal, browser, file system, web search, and calendar. it plans and executes tasks on its own. this is what you get on day one. "find flights to Lisbon under $400" "check my calendar and flag conflicts" "search the web for competitor pricing" set in Desktop app / Dashboard: Tools → enable what you need. when to use: single tasks that need tool access. 2. AGENT WITH MCP SERVERS connect your agent to external services. Notion, Google Drive, GitHub, Slack, databases, APIs, any MCP-compatible service. the agent doesn't scrape these services. it interacts through structured APIs. reads your Notion pages. creates GitHub issues. queries your database. sends Slack messages. set in Desktop app / Dashboard: MCP → Add Server. when to use: your workflow lives across multiple platforms. 3. SEQUENTIAL AGENTS (pipeline) one agent finishes. passes output to the next. assembly line for AI. agent 1: scans inbox for leads. agent 2: qualifies leads against criteria. agent 3: drafts outreach emails. in Hermes: cron jobs with wakeAgent gates. agent 1 writes output to a file. agent 2 wakes only when that file has new data. agent 3 wakes when agent 2 is done. each agent = a separate profile with its own model. when to use: multi-step workflows where each step depends on the previous one finishing. 4. PARALLEL EXECUTION AGENTS multiple agents working at the same time. results merge when all finish. "research these 5 competitors in parallel" in Hermes: delegate_task with batch mode. up to 3 sub-agents running in parallel by default. each gets its own clean context. only summaries return to the parent. delegation: model: "deepseek/deepseek-v4" children run cheap. parent synthesizes. when to use: independent tasks that don't depend on each other. research, data gathering, analysis. 5. AGENTS WITH ROUTERS conditions that send tasks down different paths based on the input. "if sales email → SDR profile. if support ticket → support profile. if calendar invite → EA profile." in Hermes: Kanban decompose. the decomposer reads profile descriptions and routes each task to the best-fit agent. or: Chief of Staff profile that triages and assigns to other profiles. when to use: incoming work that needs different specialists based on type. 6. HUMAN IN THE LOOP the agent does the work. asks for your approval before executing. "I drafted this email. approve before I send?" "this command will delete 3 files. proceed?" in Hermes: approvals.mode: manual (default). every dangerous action needs your confirmation. 60-second timeout. fails closed. or smart mode: LLM assesses risk. safe actions auto-approved. dangerous ones ask you. uncertain ones escalate. when to use: tasks where a mistake has real consequences. emails, deployments, financial transactions, public posts. 7. DYNAMIC SUB-AGENT SPAWNING your main agent realizes it needs help and spawns specialized sub-agents on the fly. "build this feature" → parent delegates: → sub-agent 1: research the API docs → sub-agent 2: write the code → sub-agent 3: write the tests in Hermes: delegate_task with role: orchestrator. raise max_spawn_depth for nested delegation. delegation: max_spawn_depth: 2 orchestrator_enabled: true depth 2 with concurrency 3 = up to 9 parallel workers. each level multiplies the spend. raise depth only when you need multi-level trees. when to use: complex tasks where the agent discovers what help it needs during execution. THE PROGRESSION: start with 1 (tools) and 6 (approvals). add 2 (MCP) when you need external services. add 4 (parallel) when tasks take too long one at a time. add 3 (sequential) when you build multi-step pipelines. add 5 (routing) when you run multiple profiles. add 7 (dynamic) when single-agent reasoning falls short. seven types. each under 90 seconds to configure. the value compounds as you stack them. comment AGENTS and I'll send you 3 ready-to-build agent setups that combine these types into real workflows.

YanXbt

17,312 просмотров • 3 месяцев назад

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 просмотров • 3 месяцев назад

Anthropic's Claude Ai Agents Team just Educated how to build production AI agents in under 30 mins. For Free. From the engineers who built the stack. CANCEL Your Weekend Plans, and Learn to Build AI Agents Today. Bookmark it. Watch it. Build your first production agent this weekend. $5,000/month. $7,000/month. $12,000/month. People are building agents for clients and charging $$$ as Beginners. You're still stuck in the thinking about AI phase. This video fixes that tonight. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward. ↓ Ivan Nardini runs Developer Relations for AI at Google Cloud. He just gave away the entire production agent stack in 30 minutes. This is the talk that separates people deploying AI agents that actually scale from people whose agents break the moment they leave localhost. Here's everything inside. I break down a production AI video like this every week. Follow Himanshu Kumar. ↓ The 4-part agent stack that actually scales. Most devs are duct-taping frameworks together and calling it an "AI agent." Ivan lays out the real stack: Agent Development Kit (ADK): open-source, code-first framework for building, evaluating, and deploying agents. Supports Claude models through Vertex AI directly. Model Context Protocol (MCP): lets your agent talk to any tool or data source with one standard. Vertex AI Agent Engine: managed platform for deploying, monitoring, and scaling agents in production. No DevOps headaches. Agent-to-Agent Protocol: open protocol so agents built on different frameworks can actually work together. This is the stack replacing every hacky agent setup in production right now. Full MCP + Claude breakdowns drop weekly on Himanshu Kumar. ↓ Building your first real agent. Ivan builds a birthday planner agent live. LLM Agent class. Name it. Define instructions. Pick the model. He uses Claude 3.7 Sonnet. You could use Opus 4.7 for better reasoning. Full agent built in minutes. Not weeks. Watch the build once and you'll never structure an agent the wrong way again. I post agent architectures people pay $500 courses to learn. Himanshu Kumar. ↓ Multi-agent systems without the chaos. Single agents are easy. Multi-agent systems are where 99% of builders fail. Ivan extends the birthday planner by: Adding a calendar service through MCP tools Creating an orchestrator agent to route requests between agents Handling state and context across agent handoffs This is production multi-agent architecture. Clean. Scalable. Debuggable. Most tutorials hand-wave this part. This one shows you every step. Multi-agent orchestration content drops weekly on Himanshu Kumar. ↓ Deployment without the DevOps nightmare. This is where most AI projects die. You build a cool agent locally. It works. You try to deploy it. Everything breaks. Vertex AI Agent Engine fixes this: Minimal code deployment Automatic monitoring of latency, CPU, and memory Built-in observability and logging No infrastructure setup needed You provide config and requirements. The platform handles the rest. This is how agents actually get to production. Deployment guides for Claude agents post every week. Himanshu Kumar. ↓ Agent-to-Agent Protocol: the future nobody's talking about. Most people don't know this exists yet. The A2A Protocol lets agents built in different frameworks communicate seamlessly. Your Claude agent. My LangChain agent. Someone else's CrewAI agent. All talking to each other. All solving parts of the same problem. All without custom integration code. This is the infrastructure layer of the coming AI economy. Getting in early on A2A Protocol is like getting in early on HTTP in 1995. A2A deep dive coming soon. Himanshu Kumar. ↓ 30 minutes from the team shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never deployed an agent past localhost. People who watch this understand production AI agents at the architect level. People who skip it keep hacking together frameworks that break every time an API updates. Save the video. Watch it tonight. Build a real agent this weekend. Follow Himanshu Kumar for more high-signal content that actually moves your AI engineering career forward.

Himanshu Kumar

229,473 просмотров • 5 месяцев назад

There are 8 billion people on earth. Soon there'll be 100 billion AI agents. Every one of them needs email. Six weeks ago I said the next wave of teams would run email through an agent instead of a dashboard. Today it ships. Nitrosend☄️ is launching Agentic Email Marketing: the email layer for the agent economy. What agents can do on Nitrosend right now: Sign themselves up. Point any agent at and it creates the account, connects your domain, sorts billing and sends its first email. No API key. No dashboard. No human required. Shipped, and users agents signing up with it daily. Get their own inboxes (beta, by request). Real addresses on the domain you own. Your agents receive, and send 1-1 email conversations with customers. A reply lands at 3am, your agent answers it. Anything that needs a human gets escalated to you. Ask us and we'll flick yours on. Next: Agentic Outreach (coming soon). Your agent studies your best customers, finds more like them, writes like a person, sends in sequence and works the replies. Then: set a goal and walk away. Goal-based agentic marketing is in development. "20% more activations this quarter" and Nitrosend plans, sends, measures and improves every week. Why we built this: Gmail is agent hostile and expensive per seat. Legacy email platforms assume a human sitting in a dashboard. agents needed an email layer of their own. They're already better at it than we are. They read everything, never miss a follow-up, and write personally at any scale. *94%* of actions on Nitrosend already happen inside an agent (Claude, Codex, ChatGPT, Cursor), not in our UI. Humans approve. Agents operate. This is our third email company. Six billion emails across the first two. We've been burned by every ugly part of email already, which is why the approval gates are built in exactly where you want them. Watch the launch, then send your agent to work: send it.

George Hartley ☄️

949,786 просмотров • 2 месяцев назад

HERMES AGENT HAS FEATURES THAT 90% OF USERS NEVER TOUCH. /BACKGROUND. /STEER. /GOAL. SUB-AGENTS. MODEL SWITCHING. CRON JOBS. 7 LEVELS OF HERMES. ALL EXPLAINED.👇 LEVEL 1 — ONE-SHOT PROMPTS you type a prompt. agent responds. done. this is using Hermes as a chatbot. it works but you leave 90% of the value untouched. LEVEL 2 — MEMORY + SOUL.MD the agent remembers you across sessions. you wrote a SOUL.md with identity, voice, restrictions. Hermes tailors every answer to your context. two people asking the same question get different answers because it knows them differently. LEVEL 3 — COMMANDS THAT MULTIPLY OUTPUT /background → fires a task in the background. your main session stays free. result appears as a panel when done. /steer → injects a message into the current run without interrupting the agent. redirects the work mid-execution. /queue → queues a follow-up for after the current task finishes. /model → switches models mid-session. start with Sonnet for planning. switch to DeepSeek for execution. switch to Opus for review. configure default behavior: display: busy_input_mode: steer # or queue, or interrupt LEVEL 4 — SKILLS + RIGHT MODEL PER SKILL every installed skill becomes a slash command: /competitive-research analyze my top 3 competitors /social-media-copy write 5 LinkedIn posts /code-review check this PR for security issues the unlock: assign a specific model per skill. research skill → GPT-5.5 (cheap, high volume). code review skill → Fable 5 (best at code). content skill → Sonnet (best at writing). you stop paying premium prices for tasks that don't need premium models. LEVEL 5 — MCPs (CONNECT YOUR WORLD) plug Hermes into the tools you already use: Gmail, Calendar, Notion, Slack, ClickUp, Granola. the agent reads your emails, checks your calendar, pulls from your project management tool, and answers questions using YOUR actual data. "what were the numbers this week?" Hermes checks ClickUp, cross-references with your goals in memory, gives a contextualized answer. caveat from the docs: keep MCPs minimal. every MCP adds tools to the context window. 15 MCPs with 10 tools each = 150 tool schemas the model reads every turn. install what you use. disable what you don't. LEVEL 6 — SUB-AGENTS + PARALLEL EXECUTION delegate_task spawns sub-agents with isolated context. batch mode runs children in parallel: delegate_task(tasks=[ {goal: "research best industries for websites", model: "deepseek-v4-flash"}, {goal: "critique the research and find gaps", model: "gpt-5.5"}, ]) max_concurrent_children: 3 (default). each child gets own terminal session and toolset. parent receives summaries when children finish. roles: → leaf (default): cannot re-delegate → orchestrator: can spawn its own workers (bounded by delegation.max_spawn_depth) LEVEL 7 — ASYNC OPERATIONS this is where the agent works without you. /goal — persistent objective across turns. judge model checks after every turn. runs until done or budget hit (default 20 turns). cron jobs — scheduled tasks on repeat. morning briefs, competitor scans, weekly reviews. wakeAgent gates for zero-token monitoring. /background — parallel tasks in current session. results delivered when ready. your main conversation never stops. the shift: from "I ask, it responds" to "it works, I review." WHERE ARE YOU? 1 → chatbot 2 → it knows you 3 → parallel commands 4 → right model per task 5 → connected to your tools 6 → sub-agents working together 7 → runs without you most people are at 2-3. the jump from 4 to 7 is where the real time savings compound. this is just the first 7. beyond this: multi-profile architecture, self-improving knowledge bases, voice mode, kanban orchestration, webhook automation, profile distributions, browser control, IDE integration, and more. comment LEVEL and I'll send you the advanced levels with setup for each. Full guide how to build 3-agent research department with Hermes 👇

YanXbt

31,551 просмотров • 3 месяцев назад