AI 资讯

My Hermes Agent Mac just received a signed, secure and monitored message from a Claude Managed Agent, and got a reply! - A solution for long runtime work, A2A ID and security. What I Built A solution that enables two agents with different owners on a shared identity network, a Hermes and a Claude Managed Agent (Claude platform) talking to each other across the internet. Every message is Ed25519 signed by the sender. Every receiver verifies the signature against a public registry and shows a blue tick before acting. Continuous Agent Monitoring A handshake proves identity once but agents in a long runtime world don't trade a single message, they hold ongoing, autonomous conversations across hours, days, and many turns. Keys get compromised, agents get swapped, a colleagues behaviour drifts, all after the initial check. ZipViz re-verifies every message signature, registry chain, freshness, and watches the stream over time for behavioural anomalies. Trust is re-earned on every turn. So this agent was who it claimed this morning," but "this agent is who it claims, on this message, right now." The demo agents on the ZipViz network: mac-her.smc.viz — Hermes Agent on my Mac Mini brendan-clau.smc.viz — Claude Agent in Cloud When Mac sends a message to brendan-clau, Mac's private key signs it. Brendan-clau verifies the signature against ZipViz's registry, and checks it just ran with the MCP (algorithm, key fingerprint, registry chain, timestamp), then replies signed. Same flow in reverse. Same flow Hermes ↔ Hermes , or Claude ↔ Openclaw . The runtime doesn't matter; the identity layer does. "I received a signed message from mac-her.smc.viz". Reads back the four checks it just ran: ✓ Algorithm: Ed25519 ✓ Key fingerprint: ab52afe... matches registry ✓ Registry chain: mac-her → smc.viz → .viz (Handshake) all resolved ✓ Timestamp: 2026-05-31 11:18 UTC, fresh Demo Hermes continuous monitoring and verification with A2A Protocol Code One MCP server: [ zipviz-mcp ] https://www.npmjs.

One of the biggest myths in the software industry is that great engineering teams are built by hiring great engineers. They aren't. I've worked with incredibly talented developers who eventually became disengaged, indifferent, and unwilling to contribute beyond the bare minimum. I've also worked with average developers who grew into exceptional engineers because they were surrounded by a culture that rewarded curiosity, ownership, and continuous improvement. The difference was never talent. The difference was culture. The Toxicity Nobody Talks About When people hear the term toxic workplace , they usually imagine shouting managers, impossible deadlines, public humiliation, and constant pressure. Those environments certainly exist. But some of the most damaging engineering cultures are far more subtle. On the surface, everything appears professional. Meetings are calm. Nobody raises their voice. Everyone speaks politely. The company presents itself as collaborative and mature. Yet beneath that polished exterior exists a culture that quietly destroys accountability and discourages anyone from caring too much. A Simple Pull Request That Revealed a Bigger Problem Recently, while reviewing a pull request, I asked a few straightforward questions: Why are we passing an empty string to a component that doesn't function without an ID? Why is a skeleton component living in a file where it doesn't logically belong? Could this conditional statement be simplified for readability? These weren't major architectural concerns. They weren't requests to redesign the application. They were ordinary engineering discussions—the kind that happen every day inside healthy teams. When Ownership Disappears What happened next was far more interesting than the code itself. Instead of discussing whether the observations were valid, the conversation immediately shifted toward ownership. Who originally wrote the code? Who moved the code? Who was responsible for introducing it? The discussion was n

Previously, we learned how to send and receive data in Go. Now, we will combine those concepts and build a simple CRUD API. CRUD stands for: C reate R ead U pdate D elete These four operations form the foundation of most backend applications. In this tutorial, we will build a simple task API in Go using only the standar library. By the end, you will understand: how CRUD APIs work how to handle multiple HTTP methods how to store data in memory how to send and receive JSON data how backend APIs manage resources Prerequisites To follow along, you should have: Go installed basic familiarity with Go syntax understanding of the net/http package basic understanding of JSON handling You can confirm if Go is installed by running: go version Step 1 — Create the Project Create a new folder for the project: mkdir go-crud-api cd go-crud-api Now initialize a Go module: go mod init go-crud-api This creates a go.mod file for managing project dependencies. Step 2 — Create the Server File Create a file called main.go . Your project structure should now look like this: go-crud-api/ ├─ go.mod └─ main.go Step 3 — Write the CRUD API Open main.go and add the following code: package main import ( "encoding/json" "net/http" ) type Task struct { ID int `json:"id"` Title string `json:"title"` } var tasks [] Task func tasksHandler ( w http . ResponseWriter , r * http . Request ) { w . Header () . Set ( "Content-Type" , "application/json" ) switch r . Method { case http . MethodGet : json . NewEncoder ( w ) . Encode ( tasks ) case http . MethodPost : var task Task err := json . NewDecoder ( r . Body ) . Decode ( & task ) if err != nil { http . Error ( w , "Invalid JSON" , http . StatusBadRequest ) return } tasks = append ( tasks , task ) json . NewEncoder ( w ) . Encode ( task ) default : http . Error ( w , "Method not allowed" , http . StatusMethodNotAllowed ) } } func main () { http . HandleFunc ( "/tasks" , tasksHandler ) http . ListenAndServe ( ":8080" , nil ) } Now let's unpack what is hap

Originally published at Perl Weekly 775 Hi there! I try to keep track of the Perl-related events. You can find them listed at the bottom of each edition of the newsletter and on the events page on the Perl Weekly web site. There you can also find a link to embed the calendar in your calendar program. There are a number of events scheduled for this month. Most of them online, so if your time-zone permits, you can join those events. The big in-person event is at the end of the month The Perl and Raku Conference in Greenville, South Carolina, USA. In the last couple of weeks I have been using various AI tools extensively. It still needs some hand-holding, but it already writes code that seems to be way better than the average code I've seen. So I wonder, would it be possible to ask one of the AI tools to convert Python libraries to Perl? You know, we have been complaining for many years that companies provide implementation for their SDK/API/client in several language, but not in Perl. We also saw that CPAN could not keep up with the growth of PyPI, npm and the other 3rd party library registries. So maybe some of you would like to explore the idea of converting some of these libraries to Perl using AI. Finally a personal note, I am planning a trip to Korea and Japan in September-October. If you live there and would have any travel recommendations, I'd love to get that. Enjoy your week! -- Your editor: Gabor Szabo. Articles Introducing ZuzuScript Toby Inkster created a programming language which blends a fairly JavaScript-like syntax with fairly Perl-like semantics, and a few other features that he hasn't really seen in many programming languages. ANNOUNCE: Perl.Wiki V 1.47, JSTree copy V 1.21 Teaching AI About the British Monarchy with MCP The site already exposes information through a traditional web interface and a JSON API. But those interfaces were designed for humans and developers respectively. MCP gives AI systems a much cleaner integration point. ANNOUNCE: Perl

This article was originally published on aicoderscope.com In early 2023, Andrej Karpathy coined the term "vibe coding" to describe a new mode of software development: you describe what you want, the AI writes the code, and you ship without reading every line. He meant it as a genuine observation about where the craft was headed. By 2026, vibe coding is the default mode for most solo developers, with AI tools handling roughly 70% of keystroke work on a typical feature. The other 30%—direction, review, judgment—still belongs to the human. The pitch is real. Solo developers can now build features that would have taken a week in a day. The bottleneck isn't code volume anymore; it's knowing what to build. That's a genuine productivity unlock. The problem is also real. Codebases vibe-coded without guardrails develop a specific pathology: inconsistent patterns across files (because each AI session starts with no memory of the last), logic errors masked by plausible-looking code, and no rollback culture because no one committed before letting the AI loose. The developer who vibed their way through six weeks of feature work often can't explain what the codebase does anymore, because they never had to think through it. This guide is not about slowing down. It's about the ten rules that let you keep the speed without the debt. The Promise vs. the Reality What vibe coding looks like in 2026: you open Cursor, describe the feature in natural language, and Agent mode writes the file. You review the diff, accept what looks right, reject what looks wrong, and move on. For standard CRUD features, state management, boilerplate API clients, and UI components, this works well. The AI has seen enough patterns that its output is often correct on the first try. Why it works especially well for solo devs: there's no code review bottleneck. A team has to slow down to onboard the AI's changes into shared mental models. A solo developer owns the whole context and can iterate without waiting fo

This article was originally published on aicoderscope.com On paper, Windsurf and Cursor are the same product. Both are standalone IDEs forked from VS Code. Both charge $20/month for their entry paid tier. Both ship a tab-completion model and a multi-file agent. Both wire in the same frontier models — GPT-5, Claude Opus, Gemini. Reviews that score them feature-by-feature end up in 47-43 ties because the feature lists genuinely match. That kind of comparison misses the point. The two editors feel different to use, and the difference matters more than the feature checklist. This piece tests both side-by-side across two weeks of normal client work — Python, TypeScript, Go — and lands on a clear verdict at the end about which one fits which kind of developer. Pricing and feature claims here were verified against Windsurf's pricing page and Cursor's pricing page on May 5, 2026. Both vendors change pricing more than most editors — re-verify before subscribing. Pricing: nearly identical The pricing tables converged in 2025 and have stayed mirrored since: Tier Cursor Windsurf Free Hobby (limited Agent + Tab) Free Entry paid Pro $20/mo Pro $20/mo Heavy individual Pro+ $60/mo (3× usage) / Ultra $200/mo (20× usage) Max $200/mo (heavy users, unlimited extra at API pricing) Team Teams $40/user/mo Teams $40/user/mo Enterprise Custom Custom Cursor offers a middle tier (Pro+ at $60) that Windsurf doesn't match exactly. Windsurf has a "Light" plan with unlimited usage on cheaper models that Cursor doesn't have. These are minor — for the typical individual developer choice, both are $20/month for Pro and $200/month for the power-user tier . The entry decision is therefore not a price decision. It's a workflow-fit decision. Both ship a standalone editor A common misconception: "Windsurf is a VS Code extension, Cursor is its own editor." Both are standalone applications. Both fork VS Code. Both can install most VS Code extensions from the Open VSX Registry (with occasional compatibility

This is a submission for the Hermes Agent Challenge : Build With Hermes Agent What I Built A small backstory on my coding origins I learnt coding by secretly studying from a python book pdf on my Computer Scientist father's work laptop. That very day I wrote a program that inputs a user's name and prints: "You are mad {name}!" and had a lot of fun pranking my brother using that script. Since then, there have been very few moments where coding felt as magical, because the more you understand syntax, the more you understand the magic underneath your code. That is, until you meet a genius piece of magic such as Hermes. My app idea I built a Fitness coach inside Hermes that learns and adapts based on your daily feedback. According to your goals, performance, and time allocated, it adjusts your current plan. For the purpose of this hackathon I tested it via terminal ui (tui) but I plan to release the polished version on chat apps such as telgram and whatsapp for painless daily checkins. Demo Code Github link My Tech Stack Hermes + node.js. Kept it simple for this quick dive. How I Used Hermes Agent Building an AI application that feels truly personal requires more than just a clever prompt; it requires state, memory, and the ability to adapt over time. During a recent hackathon, I set out to build an autonomous AI fitness coach. Not just a chatbot that spits out generic workout templates, but a system that onboards a user, sets a multi-month timeline, generates habit blocks, and adjusts daily based on feedback. To achieve this, I used Hermes , an agentic framework designed for stateful, long-running applications. Here is a breakdown of how I built it, the challenges faced, and why Hermes was the perfect tool for the job. Why This App is a Perfect Fit for Hermes Most LLM interactions are stateless. You ask a question, you get an answer, and the session ends. A fitness journey, however, is a deeply stateful process. It spans weeks or months and requires constant recalibrat

This article was originally published on aicoderscope.com On April 28, 2026, Warp open-sourced its terminal client under AGPL-3.0, picked up 60,000 GitHub stars, and declared itself an "agentic development environment." OpenAI signed on as founding sponsor. The announcement looked like a triumph of developer-first idealism. Read the fine print and a different picture emerges: the terminal is free; the product that matters — Oz, Warp's cloud agent orchestration platform — remains fully proprietary. Warp is not becoming an open-source project. It is becoming an enterprise SaaS company with an open-source frontend. None of that is inherently bad. But it is what this review is actually about: does the $20/month Build plan deliver enough AI value to justify adding Warp to a stack that probably already includes Cursor or Claude Code? What Warp is in May 2026 Warp's product now has three layers: Warp Terminal — the terminal client, open-source AGPL-3.0. Rust-based, GPU-accelerated, available on Mac, Linux, and Windows. The core terminal features (blocks, Warp Drive, session sharing, settings file) are free and remain free. Warp Agent — an AI coding agent embedded in the terminal. Runs locally for interactive work. Handles natural language command generation, code review, debugging assistance, codebase Q&A, and voice input. Consumes credits from your plan. Oz — Warp's proprietary cloud orchestration platform. Runs agents in the background, coordinates multi-agent workflows, triggers on events from Slack, Linear, or GitHub Actions, and orchestrates third-party CLI agents including Claude Code and Codex. Oz is where the enterprise pitch lives. Around 1 million developers use Warp as their primary terminal. The pivot to agentic tooling is a bet that those developers will pay to automate their workflows beyond what a local agent session can handle. Pricing breakdown Warp simplified its pricing in December 2025, replacing the old Pro/Turbo/Lightspeed tiers with two paid plans. P

Great to see Odysseus blow up this past day, local AI getting this much attention is genuinely good for everyone building in this space. Figured this is the right crowd to share what we're launching tomorrow (June 1st), since we're playing a pretty different game. A quick framing: Odysseus is a self-hosted workspace that points at engines (Ollama, llama.cpp, vLLM, cloud APIs) and runs through Docker. Conifer is the engine itself, with our own runtime, running natively on Mac, Linux, and Windows. So we're the layer underneath, not a competitor to the workspace. What's actually in it tomorrow: A native inference runtime across Mac, Linux, and Windows, with our own Metal engine for Apple Silicon already matching or beating llama.cpp on a few models on the M3 Max (full benchmarks, including where we're still behind, are at conifer.build/benchmarks) A real coding IDE on top (CodeMirror, integrated terminal, file viewers), so you can code locally with models that never leave your machine Typhoon, a local agent that can read and edit a folder you point it at, kernel-sandboxed rather than just a shell with a warning Install is a signed app you double-click, no Docker, no localhost ports Fully free and open source The honest reason we exist: PewDiePie's wave defined "local AI" in millions of people's heads as Linux + Docker + an NVIDIA rig. If you weren't on that exact setup, the conversation probably felt like it skipped you. Conifer is what local AI should feel like when it's actually native to your machine, whatever your machine is. Launches tomorrow, free and open source like PewDiePie! You can sign up for our waitlist here: conifer.build I'll be around in the comments all day tomorrow, please bring the hard questions. submitted by /u/No_Elephant_7530 [link] [留言]

The biggest headache im having is learning how to separate elements on the page correctly. I can center things and all, but dont know when to create a new section or just keep using the same since most things i can center or adjust using some propertie. Is there anywhere I can learn about something like this? i was trying to learn about the structure of websites trough the inspect in the browser(just to know what what are some best practices to adopt) and it just feels confusing. Im new to webdev, and was doing it to learn how to separate the divs on the page, then i asked claude to generate some random site just to read through the code, and simply everything is divs, like everything, no h1, title, nothing. From what i understand divs are the favorites because they dont have any set properties, and there's the thing about being able to arrive at the same result in different ways. But is it really the optimal way? Thank you in advance. submitted by /u/SkullDriv3rr [link] [留言]

Ok, so I had days long conversation with AI, but half of it disappeared, and now it's giving me different answers than it was before. submitted by /u/Melora1976 [link] [留言]

NVIDIA claims the new RTX Spark chip for PCs will offer 1 petaflop of AI computing power.

Without revealing too much information, what were the circumstances? submitted by /u/XTXinverseXTY [link] [留言]

Once upon a time, Microsoft had to write off $900 million betting an Arm-based Nvidia chip could power its first flagship Windows portable, the original Microsoft Surface. But today, it's trying again. Microsoft and Nvidia have just announced the Surface Laptop Ultra, a computer with a new Arm-based Nvidia chip at its core. There's a […]

With all the talk about AI companions and autonomous agents, I’ve been experimenting with building a more personal, always-on assistant that runs locally or on your own hardware. The goal wasn’t just another chatbot — it was something that could handle voice conversations, manage ongoing tasks across different platforms (chat apps, scheduled triggers, etc.), remember context over long periods, and delegate work without constant babysitting. What stood out in practice • One consistent “brain” across everything — Whether you’re talking to it via voice, Telegram, a web interface, or it wakes up on a schedule, the core reasoning, memory, and tool use stay the same. This eliminated a lot of the fragmentation you see in many current agent setups. • Modular extensions — Different capabilities (voice, different chat networks, external tools, long-term memory consolidation) plug in cleanly. This made it easier to add or swap things without rebuilding the whole system. • Persistent and proactive — It can maintain memory across days/weeks, run background tasks, and even hot-reload its configuration when you change settings. The result is something that starts feeling more like a digital collaborator than a question-answering box. A quick feel for the voice interaction style is here: https://youtube.com/shorts/NGIi8sliooU I open-sourced the harness (called Maven) under an MIT license for anyone interested in running or extending their own version: https://ageneral.ai/maven I’m curious how others are thinking about personal agent setups in 2026. • Do you prefer fully local models, cloud APIs, or a mix? • What capabilities feel most missing from today’s consumer AI assistants? • How important is “owning” your agent data and runtime vs. using polished third-party services? Would love to hear experiences or concerns from both technical and non-technical users. submitted by /u/qasimsoomro [link] [留言]

The row looked perfect. rating: 7 . Valid JSON, right type, no nulls, no missing keys. My schema check waved it through. The page had returned HTTP 200. The selectors hadn't moved. Everything green. A rating of 7 on a 5-star site is impossible. The model invented it, formatted it correctly, and handed it to me with total confidence. That's the failure I want to talk about. Not the scraper that breaks loudly. The one that hands you a clean-looking row that is quietly, plausibly false — and sails past every check you have, because your checks are all looking at the shape of the data, and the lie is in the value . TL;DR HTTP 200, intact selectors, and valid JSON tell you the form is fine. They say nothing about whether the value is true. When an LLM extracts from messy free-text, structured-output mode guarantees you get valid JSON. It does not guarantee the content is real. The model fills uncertain fields rather than leaving them empty — because the schema demands a complete row. A ~60-line value-level sanity gate (ranges, dates, cross-field, reference, language) catches the obvious lies before they hit your database. Real code and real output below. The honest catch: this gate catches rule violations , not plausible lies inside the allowed range . A rating: 4 where the truth is 2 slides right through. I'll be specific about where the gate stops. Two different ways a scraper lies to you I wrote about source drift last week — the case where the page changes underneath you and a 30-line schema check catches the structure shifting. That's an input problem. The source mutated; your agreement with the page broke; you detect it by watching the shape. This is the other end of the pipe. The source is fine. The page is intact, the selectors are correct, the structure is exactly what you expected. The thing that lied to you is the model , on the extraction step, when you asked it to pull structured fields out of a paragraph of human prose. Those two failures feel similar and t

I spent way too long staring at this error. If you're here, you probably are too. Your requirements could not be resolved to an installable set of packages. Problem 1 - Root composer.json requires php ^8.3 but your php version (8.2.30) does not satisfy that requirement. My Laravel 13 app needed PHP 8.3. My Hostinger server was running 8.2. composer install refused to budge. Here's exactly what happened and the one-liner that fixed it. The Setup I was deploying a Laravel 13 + Inertia + React app to Hostinger shared hosting. Laravel 13 requires PHP 8.3 minimum — and so do its locked Symfony 8.x and PHPUnit 12.x dependencies. My composer.lock had been generated on a local machine with PHP 8.3, but Hostinger's CLI was defaulting to 8.2. The hPanel showed PHP 8.3 selected under PHP Configuration . The website itself was running fine on 8.3. But SSH? Still on 8.2. $ php -v PHP 8.2.30 ( cli ) That disconnect — hPanel vs. CLI — is the trap. What I Tried First composer update My first instinct was to just let Composer resolve newer compatible versions: composer update No luck. The root composer.json itself declared "php": "^8.3" , so Composer refused before even touching the lock file. The PHP constraint wasn't just in dependencies — it was in my own project requirements. composer install --ignore-platform-reqs This flag skips platform checks and forces the install anyway. It works , but it's a lie — you end up with packages that may behave incorrectly or fail at runtime because they genuinely require PHP 8.3 features. Not a real fix. Changing PHP in hPanel Hostinger's control panel has a PHP version switcher under Hosting → Manage → PHP Configuration . I had already set this to 8.3. This controls the web server / FPM version — what runs your .php files in the browser. It does not change what php points to in your SSH terminal. That's the key distinction most tutorials miss. What Actually Fixed It Hostinger installs multiple PHP versions in parallel. They live in /opt/alt/ph