AllyshipContent Radar

News 1647

Chủ đề cộng đồng đang thảo luận

Crawl live-1795068900000 · 13:22 19 thg 11, 2026 · Xuất bản 14:10 19 thg 11, 2026

171 / 1647 chủ đề đạt ngưỡng 55 trong khoảng này.

83

A new way to dig into how your agents work together. Explore their boards and see how they exchange knowledge.

62

2 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

carmahhawwari, amasad 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

A new way to dig into how your agents work together. Explore their boards and see how they exchange knowledge. Media

84

Show HN: KradleBench – Multi-agent AI evals in Minecraft

62

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 15 tương tác đã đo · Nguồn crawl

jamest 1 bài viết · HN: LLM
Nguyên văn nguồn
Chi tiết nguồn

Hi HN - This is James and Kemal. In past lives we led Firebase and Tensorflow/JAX respectively. HN has been a particularly big part of my (James’) career and the trajectory I’ve taken would be meaningfully different without it. Thank you! Our team shipped a benchmark: KradleBench. We test AI in Minecraft Worlds. 1. The worlds are multi-agent. Humans and other AIs are in there too, often pursuing their own goals. Collaboration and conflict skills fall out of this property. 2. The world are dynamic. They constantly change, which means that agents need to react. “Capture the Flag” has a single winning condition, and many different ways to achieve it. This leads to many emergent and creative strategies. 3. The worlds are real-time. They are not turn-based, they do not wait for AIs to finish thinking. Nature balanced speed and intelligence in humans, we can understand this in AIs too. Underneath all this is Kradle, a platform to test and understand intelligence. It’s a petri dish where any intelligence type (LLM, World Model, Human) can be compared and generate useful information to improve current systems, whether it’s on capabilities or safety. Some findings so far: - A skilled human was #1, until yesterday when Astra 6.2 surpassed them. We lose badly on solo tasks and out-compete on multi-agent ones - Astra 6.2 iterates on its strategy 4x faster than Fable 5.2. The Claude family tends to think hard and stick with strategies. The OpenAI models tend to be more reactive and iterative, which serves them well in multi-agent, dynamic, real-time evals. We’ve got videos on all the top model’s page, and we’ll be producing them when a new model launches. Sign up on the site to get them and for when the platform opens. Thanks for reading, James & Kemal

89

Show HN: A deterministic typesetting tool for Orthodox Music

60

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 7 tương tác đã đo · Nguồn crawl

rpmisms 1 bài viết · HN: Claude
Nguyên văn nguồn
Chi tiết nguồn

I'm a trained Russian Orthodox church musician and software developer. I figured I would flog my Claude Pro subscription into helping me create a deterministic engine for typesetting church music that would otherwise be sung off of text alone in most cases. No AI is used in processing any of the texts, it's entirely algorithmic. Even if you don't have a use case for this, I figured the music nerds out there might appreciate taking a look at it and even perhaps giving a suggestion on how to improve it.

91

Show HN: Re-SiON – 40kb software synthesizer library that plays plaintext files

59

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 5 tương tác đã đo · Nguồn crawl

popcar2 1 bài viết · HN: GPT
Biên tập tiếng Việt
Chi tiết nguồn

Người viết giới thiệu Re-SiON là một bản triển khai lại thư viện synthesizer phần mềm cũ do Adobe Flash tạo ra. Họ nói dự án rất nhỏ (khoảng 40KB) và chạy trên web lẫn desktop. Re-SiON có thể phát các file MML văn bản thuần dễ chỉnh sửa; nhiều bài mẫu chỉ chiếm vài kilobyte. Dự án có playground để chơi và chỉnh MML realtime, và có bộ chuyển đổi từ tracker formats và từ nhạc NES/SNES/GameBoy/Genesis sang MML. Tất cả mã nguồn là open source theo MIT và có nhiều ví dụ để nghe.

Hi HN! Re-SiON is a re-implementation of an old software synthesizer created for Adobe Flash. It's incredibly tiny (at ~40KB) and runs on the web and desktop platforms. It plays easily editable plaintext MML (Music Macro Language) files which are insanely tiny, many example songs only taking up a few kilobytes. The project also comes with a playground to play and edit MML in real time, and a converter that can convert from tracker formats and NES/SNES/GameBoy/Genesis music straight to MML. It's all open source under MIT, and the link has a bunch of example songs to listen to. Happy to answer any questions.

  • It's incredibly tiny (at ~40KB) and runs on the web and desktop platforms.
  • It's incredibly tiny (at ~40KB) and runs on the web and desktop platforms.
  • It plays easily editable plaintext MML (Music Macro Language) files
  • It's all open source under MIT
92

LangSmith cho coding agents: theo dõi chi phí theo đầu ra

61

1 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · chưa có số tương tác · Nguồn crawl

langchain 1 bài viết · LangChain Blog, X
Biên tập tiếng Việt
Chi tiết nguồn

LangSmith cung cấp báo cáo dành cho coding agents, kèm các khả năng mới liên kết chi phí của họ với các pull requests mà họ tạo ra.

LangSmith now offers reporting built for coding agents, along with new capabilities that tie their spend to the pull requests they produce.

  • LangSmith now offers reporting built for coding agents, along with new capabilities that tie their spend to the pull requests they produce.
  • LangSmith now offers reporting built for coding agents
  • tie their spend to the pull requests they produce.
95

Launch HN: Maritime (YC F26) – A managed cloud for production AI agents

67

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 91 tương tác đã đo · Nguồn crawl

ashriv 1 bài viết · HN: LLM
Nguyên văn nguồn
Chi tiết nguồn

Hi HN, we're Ary and Maria, co-founders of Maritime ( https://maritime.sh ). We're building an agent-native cloud that handles everything from custom environments to lifecycle management for AI agents. Demo: https://www.youtube.com/watch?v=lCWMdBQ96rY There’s been an explosion of sandbox companies coming out of SF, but sandboxes solve maybe 10% of the infrastructure problem for AI agents. The approach that most sandboxing companies take is: You buy Hetzner/OVH Cloud bare metal servers, use Firecracker to slice the servers up into VMs, sell those VMs with low margins. It’s a bit of an oversimplification, but the point is it’s a narrow solution to a fairly difficult problem. We talked to a couple hundred companies that are building AI agents. From personal assistants and coding agents to specialized healthcare agents, and the main pattern we saw was that even after choosing a sandbox provider, you still have to build additional infrastructure just to get things working. These were the primary points of friction: 1. Agent lifecycle management. There’s a lot that you have to build in order to properly give your agents VMs: things like sleep/wake, persistent storage, triggers, scheduling, per-user routing and spend caps, health monitoring, failure recovery, and deploying updates across thousands of VMs without downtime. There are so many of these small sandbox management tasks that companies have to build and maintain themselves, and they add up. 2. Custom environments. Production agents have varying needs. Some agents need Windows applications. Others need Android, browsers with persistent sessions, custom operating system images, preinstalled desktop software and applications, or specific dependencies. Some agents need access to private networks to interact with customer-specific things on prem, or residential IPs, or the ability to restrict network access completely. 3. Cost optimization. If you’re selling a personal assistant for $20/month, a sandbox that costs $0.04/hour comes out to roughly $29/month if you keep it running continuously, not including LLM inference, storage, etc. There is a way to combat this though, which is to optimize sandbox usage with auto-snapshotting, making things event-driven, mounting S3 buckets to agent environments via FUSE for cheap storage, cold-tiering snapshots, etc. All roads lead to… building more infrastructure. So what did we build differently? We give each agent its own isolated, persistent microVM and a configurable environment. On top of the compute, we built a lot of composable services: provisioning, persistent state, sleep/wake orchestration, triggers, schedule creation, monitoring, network configuration, updates, rollbacks, recovery, per-agent spend tracking, login handoffs, all the things you’d need for production agents. We also spent a huge amount of time optimizing cost. A lot of thought was put into things such as scale-to-zero, copy-on-write over shared base images, compressed memory snapshots, hot/warm/cold snapshot and disk tiering, and other optimizations while balancing these with performance metrics like latency. As a result, Maritime costs $1 for a 2gb RAM agent per month (unlimited usage for that $1), with additional resources available as needed. Maria was a visiting lecturer at MIT and did research at Project NANDA on agent infrastructure. Ary did research on agent coordination protocols at the same lab. We started Maritime together this March because of all the issues we faced with trying to deploy agents to the cloud during our research. We want your feedback. If you're building an agent product, what did you have to build on top of sandboxes to make them work? We want to know about all the workarounds and weird things you’ve had to build. Are there things you’ve tried to build with VMs but couldn’t? Does Maritime fit your needs? Is there a feature we’re missing that would make us more enticing? Happy to answer any questions in the comments. https://maritime.sh

96

Show HN: Reprise, a read-later app with narration on the neural engine for iOS

59

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 5 tương tác đã đo · Nguồn crawl

jeffd 1 bài viết · HN: GPT
Nguyên văn nguồn
Chi tiết nguồn

I've been working on this app for a little under a year now. I've gotten PocketTTS working with voice cloning running on an iPhone's neural engine, at speeds where you can narrate an article that has 20 minutes of audio in under 20 seconds.

99

Show HN: Mastra Factory, the open-source software factory we use to build Mastra

67

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 121 tương tác đã đo · Nguồn crawl

codekarate 1 bài viết · HN: LLM
Nguyên văn nguồn
Chi tiết nguồn

Hi HN, we're Shane, Sam, and Abhi. Almost two years ago, we shared Mastra, our open-source TypeScript agent framework, on Show HN: https://news.ycombinator.com/item?id=43103073 . It got a few hundred upvotes; a couple of weeks later our downloads had doubled, and we were off to the races. Today we're sharing Mastra Factory, the open-source software factory we built to help maintain Mastra itself. At Mastra, we now average nearly 4M downloads per week, and with Factory our team now merges hundreds of PRs a week across the mastra-ai GitHub org. Last week, Factory opened and merged 238 PRs, alongside 630 merged PRs from humans. There's a lot of debate about what a software factory is. For us Factory is a configurable agentic kanban board that's @-taggable in Slack. Under the hood, it uses Mastra’s durable agents for long-running sessions, our conversational memory system, a markdown based wiki with source citations to incorporate company knowledge, signals that subscribe to PR comments wired up into sessions, and a customizable cloud sandbox with our coding harness (working on supporting Claude Code, Codex etc). When we started out, we modeled Factory around our existing workflow-oriented process (triage, plan, build, review, shipped). Three months later, we find ourselves mostly driving it through Slack vs a web UI. We’ve seen more senior engineers kick off sessions in parallel (“triage the 20 oldest issues and let’s evaluate…”). We’re using bug and vuln scanners now, and we’ve closed our repo to outside contributors, asking folks to write detailed issue repros instead. You can get started with `npm create factory`. It’s fully open-source, so you can run it entirely on your infra (we also offer a hosted version). Comment here, we would love to know what you think! https://factory.mastra.ai https://github.com/mastra-ai/template-factory

100

Show HN: Can an AI Agent Bypass Your Website Security?

60

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 9 tương tác đã đo · Nguồn crawl

timshell 1 bài viết · HN: GPT
Nguyên văn nguồn
Chi tiết nguồn

As part of our red-teaming efforts, we recently configured GPT-6 Astra to test how easily an AI agent can bypass existing bot detection and human verification systems. We built a tool that lets you run the same test on your own website: https://assess.poh.org Enter your website URL, and we'll launch an AI agent to test your workflows, record its actions, and show how we evaluate the session. Below are three recorded tests. In the recorded tests below, agents were able to complete CAPTCHAs, bypass existing bot detection mechanisms, create and verify accounts, access gated resources, and carry out end-to-end workflows intended for humans. Hugging Face: https://assess.poh.org/test/2d75a3b713e2719e87a4b85c6b3aff70 (bypassed hCAPTCHA) Cloudflare: https://assess.poh.org/test/0eb218ca6e2d7be993b689dd69a1cb20 (bypassed Turnstile) YouGov: https://assess.poh.org/test/144f6d014fbf006b61ec6bc32ee8c3f4 (bypassed reCAPTCHA) AI agents are ushering in a new age of online security, and we’re excited to hear your thoughts!

81–100 / 171
Trang 5 / 9