AI Agents

171 posts

kakao3 min readCurated summary

Is a Non-Developer Who Does Vibe Coding a Developer? (3)

AI coding agents have helped a non-developer move from creating small local HTML tools to building shared dashboards, integrations, automations, and repeatable workflows. The major change was not writing more code, but learning to define data, permissions, inputs, outputs, exceptions, and validation criteria. The author concludes that AI is making more kinds of work executable and structured, expanding questions about “development” beyond professional developers. ## From Local HTML to Shared Tools - Early tools were standalone HTML files used locally in a browser. - Sharing them introduced deployment, URLs, version updates, and maintenance concerns. - Once users needed persistent data and changing states, the problem expanded from UI design to: - Data storage - Access and edit permissions - Change history and rollback - Backups and operational responsibility - Google Sheets became a practical lightweight database because it already provided: - Collaboration and familiar interfaces - Permission management - Revision history - The author progressed from manually pasting Apps Script code to using `clasp` and Apps Script APIs for deployment and execution. - The key shift was learning to evaluate where data should live and which tools already work safely within an organization. ## Security as a Daily Habit - Connecting work tools through webhooks introduced the need to protect tokens and webhook URLs. - The author began using `.env` files and `.gitignore` to prevent secrets from entering source code or Git repositories. - Requests to AI agents increasingly included security requirements: - Read secrets from environment variables - Avoid printing sensitive values in logs - Use placeholders instead of real credentials - Small automations connected to external systems naturally required thinking about secret management, execution environments, and access control. ## Turning Manual Tasks into Workflows - Tasks such as copying files, organizing folders, converting documents, editing videos, and extracting audio or summaries were delegated to AI agents. - Delegating these tasks required explicit definitions of: - Input files - Output names and formats - Whether existing files may be overwritten - Failure conditions - Verification requirements - Informal, intuitive actions became structured work specifications. - The author found that understanding completion criteria and input/output formats was often more important than memorizing individual commands. ## Skills and Feedback Loops - Weekly meeting-note preparation revealed recurring editing patterns and implicit business rules. - These rules were encoded into Codex and Claude skills covering: - Note structure - Action-item extraction - PMO-related signals - Situations where the AI should ask questions instead of making assumptions - Skills functioned as stored decision criteria, not merely collections of prompts. - Comparing AI-generated drafts with the author’s final revisions enabled continuous refinement. - Deleting local data for security reasons accidentally removed useful conversation context, temporarily reducing skill quality and demonstrating the importance of preserving relevant operational knowledge. ## Using Outputs as New Inputs - Google Analytics reporting became more frequent and detailed through MCP-based API access and reusable reporting skills. - MCP provided the data connection, while skills preserved the recurring monthly report structure. - The valuable work remained interpreting changes between periods and deciding whether a change was meaningful. - Combining AI-generated metrics with the author’s contextual knowledge helped surface signals requiring further investigation in near real time. The author recommends focusing less on how much code AI can generate and more on how work can be clearly structured for AI execution. As agents become more capable, everyone—not only developers—will increasingly define inputs, outputs, permissions, security controls, repetition, and validation as part of everyday work.

Read original(opens in new tab)
aws4 min readCurated summary

AWS Weekly Roundup: AWS FinOps Agent in preview, Gemma 4 on Bedrock, Kiro Pro Max, and more (June 15, 2026) | Amazon Web Services

AWS’s June 15, 2026 roundup highlights rapid adoption of AI-native development, a preview of the AWS FinOps Agent, and major infrastructure and model releases. AWS reports significant productivity gains from agent-assisted engineering, while new services target cost optimization, observability, security, and developer workflows. The overall direction is toward more autonomous, context-aware tools integrated throughout the AWS ecosystem. ## AI-Native Development at AWS - Amazon engineering teams are restructuring development around AI agents. - A six-engineer team rebuilt the Amazon Bedrock inference engine in 76 days, compared with an original estimate of 30 developers over 12–18 months. - Structured Amazon Stores pilots achieved a median 4.5× improvement in normalized deployment velocity, with some teams exceeding 10×. - Recommended practices for “frontier teams” include: - Building steering files, coding standards, and structured repositories to provide agent context. - Expecting an initial productivity slowdown while workflows change. - Maintaining a backlog of well-scoped tasks that agents can execute in parallel. - Writing structured specifications before generating code. - Moving testing earlier so agents can detect and correct issues. - AWS cautions that commit velocity is only one measure; future work will address release management, operations, security, and end-of-life upgrades. ## AWS FinOps Agent Preview - AWS FinOps Agent helps finance and engineering teams: - Answer AWS cost questions and generate reports. - Identify rightsizing, idle-resource, and Savings Plans opportunities. - Investigate cost anomalies automatically. - Schedule recurring FinOps workflows. - Recommendations come from AWS Cost Optimization Hub and AWS Compute Optimizer. - The agent can open Jira tickets and post anomaly-investigation findings to Slack. ## New EC2 M9g and M9gd Instances - M9g and M9gd instances use AWS Graviton5 processors and the sixth-generation Nitro System. - They provide: - Up to 25% better compute performance than Graviton4. - Up to 35% faster web applications and ML inference. - Up to 30% faster database performance. - Up to 15% more network bandwidth and 20% more EBS bandwidth than M8g. - Graviton5 adds PCIe Gen6, DDR5-8800 memory, and a 5× larger L3 cache. - The Nitro Isolation Engine uses formal verification to provide mathematically proven VM isolation. - M9gd adds up to 11.4 TB of local NVMe SSD storage and 30% higher IOPS than M8gd. - Instance Bandwidth Configuration can shift bandwidth between EBS and VPC networking by up to 25%. ## Bedrock Model Updates - Anthropic Claude Fable 5 launched on Bedrock with: - Extended asynchronous task execution. - Advanced vision for diagrams, charts, and PDFs. - Proactive self-verification. - Access required Data Retention API opt-in and 30-day retention for inputs and outputs. - Anthropic later asked AWS to revoke access to Claude Fable 5 and Claude Mythos 5 in response to a U.S. government export-control directive. - Google DeepMind’s Gemma 4 models are available in three versions: - Gemma 4 31B for reasoning and coding, with a 256K-token context window. - Gemma 4 26B-A4B, a mixture-of-experts model for cost- and latency-sensitive use. - Gemma 4 E2B for low-latency interactive applications. - All variants support function calling, structured output, reasoning, streaming, multimodal inputs, and more than 35 languages. ## OpenSearch MCP Apps for Agentic Observability - OpenSearch MCP Apps bring logs, traces, metrics, and alerts into compatible agentic environments such as Claude Desktop and VS Code. - Agents can investigate incidents across OpenSearch and Amazon Managed Service for Prometheus. - Each tool call produces both: - A text summary for the agent. - An interactive visualization displayed in the conversation. - Available tools cover log, metric, and trace analysis; service performance; topology; agent health; cluster health; dynamic visualizations; and instrumentation scoring. ## Additional AWS Updates - AWS CLI v1 is entering maintenance mode: - Dependencies such as `botocore` and `s3transfer` will be vendored into the CLI. - Future releases will focus on critical bugs and security fixes. - AWS recommends migrating to CLI v2. - AWS Workload Credentials Provider provides short-term credentials for applications running outside AWS, including on-premises and third-party environments, without requiring long-term access keys. - Kiro Pro Max adds higher usage limits, access to newer frontier models, and additional agentic development capabilities for professional teams. AWS’s latest releases suggest that teams should prepare for AI agents to handle not only code generation, but also cost management, observability, testing, and operational workflows. Migrating to AWS CLI v2, evaluating Bedrock’s newest models, and establishing strong repository context and specifications are practical next steps.

Read original(opens in new tab)
github1 min readCurated summary

Making secret scanning more trustworthy: Reducing false positives at scale

Mariko is a Principal Applied Scientist at Microsoft who leads the development of agentic AI workflows for cybersecurity operations. Her work centers on using large language models and agentic systems to bring frontier AI research into practical products and operational environments. ## Professional Role - Principal Applied Scientist at Microsoft. - Leads agentic AI workflow development for cybersecurity operations. ## Research and Technical Focus - LLM-powered systems. - Agentic workflows. - Applying frontier AI research to real-world products and operations. Overall, Mariko’s work connects advanced AI research with practical cybersecurity and enterprise applications.

Read original(opens in new tab)
stripe2 min readCurated summary

Stripe Projects adds new agent integrations, more providers, and custom developer controls

Agent traffic now exceeds human internet traffic, driven largely by agents independently building software and integrating APIs. Stripe reports that agents account for nearly 40% of its documentation traffic and 70% of API-resource requests through the Stripe CLI. Stripe Projects is expanding to help agents handle the infrastructure, credentials, services, and operational controls surrounding software development. ## Agent Integrations - Stripe Projects is available as a skill in Hermes, an open-source AI agent from Nous Research. - Hermes can retain context across sessions, allowing it to collaborate on complex projects over days or weeks. - Factory Droids and Warp have integrated the Projects CLI into their coding workflows. ## Expanded Provider Support - Projects now supports 49 providers, adding 16 new integrations. - New providers include: - Metronome for usage-based billing - Wix for storefronts - ClickHouse for LLM observability - Agents can provision applications, billing, storefront, monitoring, and other services without manually navigating provider dashboards. ## Controls for Safe Agent Provisioning Stripe is adding guardrails similar to those used for agent-driven purchases: - **Unified cost visibility:** Developers can view current and historical spending across providers for each project. - **Per-provider spending limits:** Teams can set different caps for services such as AI models, hosting, and databases. - **Named environments:** Isolated credentials can be created for development, staging, production, or custom environments. Agents default to development, reducing the risk of affecting production. - **Platform delegation:** Platforms can provision services for users using scoped credentials and white-labeling, keeping developers inside the platform’s environment. ## Future Direction Stripe plans to extend Projects across the full lifecycle of agent-built software, including operations and security. Planned additions include stronger security primitives for autonomous agents and a data layer that lets providers meter and bill for software created by agents. Stripe’s broader recommendation is to use Projects as an agent-accessible way to provision infrastructure—for example, asking an agent to add a Prisma database.

Read original(opens in new tab)
slack3 min readCurated summary

Agentic Testing: Where Agents Fit in the E2E Testing Stack

Agentic E2E testing validates whether users can achieve goals rather than enforcing one fixed sequence of UI actions. Slack’s experiment with more than 200 runs found that agents can reliably explore workflows, especially through Playwright MCP, but they are slower and more expensive than deterministic tests. The conclusion is that agents should complement—not replace—traditional E2E tests. ## Goal-Based Testing vs. Fixed Journeys - Traditional tests follow predefined steps: click, type, navigate, and assert. - Agent-driven tests receive a goal and adapt their actions to reach it. - Agents may use different paths to achieve the same result, such as: - Selecting a search suggestion or pressing Enter - Reusing existing navigation state or reopening a view - Adding or skipping intermediate actions - This flexibility improves exploration but introduces tradeoffs in reliability, runtime, and cost. ## Experiment Design Slack evaluated three execution models across more than 200 runs: - **Agent + Playwright MCP** - Uses predefined browser actions and persistent DOM snapshots and logs. - **Agent + Playwright CLI** - Runs Playwright commands through the shell and reassesses the UI after each step. - **Generated Playwright tests** - Produces deterministic test code from natural language, then iteratively refines it. The experiments used Claude Sonnet 4.5 for MCP and CLI workflows and Claude Opus 4.6 for generated tests. All tests ran in non-production Slack workspaces using test data. Two workflows were tested 20 times per configuration: - **Thread Reply:** A simple 15–20-step flow involving channel creation, messaging, thread replies, and verification. - **Search Discovery:** A 25–30-step flow involving search, result navigation, channels, threads, and state verification. Inputs were provided either as detailed natural-language instructions or structured YAML describing actions and expected outcomes. ## Results: Reliability, Cost, and Runtime | Approach | Thread Reply failures | Search Discovery failures | Average runtime | |---|---:|---:|---:| | Agent with Playwright MCP | 0% | Approximately 12% | 5–8 minutes | | Agent with Playwright CLI | Approximately 12% | Approximately 20% | 9–11 minutes | | Generated Playwright tests | Approximately 8% | Approximately 48% | About 3 minutes | - Playwright MCP was the most reliable agentic approach, particularly for simple workflows. - Playwright CLI failed more often due to authentication, navigation timing, and session instability. - Generated tests were fast and reasonably successful on simple flows but degraded sharply as workflows became more complex. - Generated tests often completed 70–80% of a complex workflow before failing on a final interaction or assertion. ## Why Complexity Exposes Differences - MCP maintains a live, stable view of the application through persistent context. - CLI-based agents reconstruct state from updated snapshots, allowing small timing or interpretation inconsistencies to accumulate. - Generated tests can suffer from: - Variable UI state - Imprecise element targeting - Mismatches between generated code and existing page-object abstractions - The results suggest agent-native execution models handle increasingly complex exploratory flows better than generated deterministic tests, despite taking longer. Agentic testing is best used as an exploratory layer for validating user goals and discovering unexpected paths. Deterministic Playwright tests remain preferable for fast, repeatable regression checks, while Playwright MCP appears to be the strongest option when flexible, goal-oriented E2E coverage is needed.

Read original(opens in new tab)
aws3 min readCurated summary

Now available: Amazon EC2 M9g and M9gd instances powered by new AWS Graviton5 processors | Amazon Web Services

AWS has generally released Amazon EC2 M9g and M9gd instances, powered by its Graviton5 processors. They deliver higher compute, memory, networking, and storage performance while improving energy efficiency and security. M9g targets general-purpose workloads, while M9gd adds up to 11.4 TB of local NVMe SSD storage for low-latency applications. ## Graviton5’s Performance Improvements - Graviton5 provides up to: - 25% better compute performance than Graviton4 - 35% faster web applications and ML inference - 30% faster database workloads - It includes: - 192 CPU cores - Five times more L3 cache - Up to 33% lower inter-core latency - DDR5-8800 memory - PCIe Gen6 support - These features improve concurrency, memory bandwidth, and CPU-heavy workloads such as agentic AI, code generation, real-time reasoning, and multi-step orchestration. - Customer results include: - ClickHouse: 36% better performance than M8g without code changes - Honeycomb: 36% higher throughput per core - HubSpot: up to 60% shorter MySQL query duration ## Networking and Storage Enhancements - M9g and M9gd provide: - Up to 15% higher network bandwidth - Up to 20% higher EBS bandwidth on average - Up to twice the network bandwidth on the largest instance - Instance Bandwidth Configuration lets customers shift bandwidth between EBS and VPC networking by up to 25%. - This is useful for databases, query processing, logging, and other workloads with demanding I/O requirements. ## Nitro Isolation Engine - M9g and M9gd introduce the Nitro Isolation Engine, an enhancement to the AWS Nitro System. - It isolates virtual machines by controlling access to: - Memory - CPU register state - I/O devices - The component uses formal verification to mathematically prove isolation behavior rather than relying solely on testing. - AWS describes Nitro as the first formally verified cloud hypervisor. ## M9g General-Purpose Instances - M9g instances provide one vCPU per 4 GiB of memory. - Suitable workloads include: - Application servers and microservices - Web applications and containerized applications - Midsize data stores and caching fleets - Gaming servers - Large-scale Java applications - Code repositories - Agentic AI workloads ## M9gd Instances with Local NVMe Storage - M9gd adds up to 11.4 TB of local NVMe SSD storage. - It offers up to 30% higher IOPS and storage performance than Graviton4-based M8gd instances. - Recommended for: - Low-latency caches and scratch files - Data and log processing - Media processing - Batch workloads - Key-value stores - Gaming and application servers ## Availability and Migration Resources - M9g and M9gd are available in: - US East (N. Virginia) - US East (Ohio) - US West (Oregon) - Europe (Frankfurt) - Purchasing options include Savings Plans, On-Demand, Spot Instances, Dedicated Instances, and Dedicated Hosts. - AWS provides a Graviton Getting Started Guide, Graviton Savings Dashboard, and AWS Transform for migrating Java applications from x86 to Graviton. Organizations seeking better compute efficiency, higher I/O throughput, or lower-cost Arm infrastructure should evaluate M9g for general-purpose workloads and M9gd when local NVMe storage is required.

Read original(opens in new tab)
gitlab4 min readCurated summary

Introducing GitLab Orbit

GitLab Orbit is a public-beta, queryable graph that connects code with merge requests, pipelines, deployments, vulnerabilities, incidents, and ownership. GitLab argues that this unified context makes AI agents faster, more accurate, and capable of answering cross-system questions that traditional file search or RAG cannot. In testing, Orbit improved code-review accuracy while reducing agent runtime, token use, and hallucinations. ## The Problem with Code-Only Agents - Agents often struggle to understand the systems surrounding code: - Related files and dependencies - Tests and pipelines - Deployments and environments - Vulnerabilities and ownership - Work items and merge requests - In large or multi-repository codebases, agents can waste tokens exploring irrelevant paths, miss dependencies, or run out of context. - This can produce code that appears correct but is later reverted or requires substantial human correction. ## Results from Compare the Market - Compare the Market tested four context-retrieval approaches across 79 real merge requests. - An Orbit-grounded AI reviewer: - Placed accurate inline comments about 70% of the time. - Outperformed RAG, which achieved roughly 58%. - Produced slightly better summaries of key changes: 68% versus 66%. - RAG performed worse than the other tested approaches, including using no additional context. ## Faster and More Efficient Coding Agents - Claude Code and other agents can connect to Orbit through the Model Context Protocol (MCP). - Instead of crawling a repository to infer relationships, an agent can query the graph directly for: - Where code is located - What depends on it - Which tests and pipelines cover it - GitLab reports up to: - 11× faster execution - 4.5× lower token usage - 45× fewer hallucinations ## Cross-System Engineering Workflows Orbit enables agents on the GitLab Duo Agent Platform to investigate relationships beyond source code. - **Pipeline failure triage** - Agents can identify merge requests associated with a failing job. - They can find other projects and in-flight changes likely to encounter the same failure. - This can help teams resolve shared incidents centrally rather than repeating investigations. - **Vulnerability blast-radius analysis** - Queries can trace vulnerable components through services, pipelines, environments, and owning teams. - Security teams can produce assigned remediation plans shortly after a CVE is discovered. - **Engineering metrics** - Teams can query relationships between cycle time, pipeline failure rates, and deployment frequency without waiting for custom dashboards or SQL analysis. - **Migration planning** - Orbit identifies dependent services, jobs, environments, and owners. - This reduces the risk of discovering hidden dependencies late in a migration. ## Architecture and Access - Orbit ingests lifecycle data through change-data capture into ClickHouse. - It parses code in 12 languages, including Ruby, Java, Python, TypeScript, Rust, Go, C#, C++, and PHP. - GitLab reports indexing more than: - 40,000 projects - 500 million nodes - 2 billion edges - The graph can be queried through: - A Cypher-like query language - MCP - REST - The GitLab CLI - An event-driven engine keeps the graph current as changes occur. - Indexing runs separately from GitLab, so query traffic does not burden the GitLab instance. - Authorization follows existing GitLab permissions, limiting agents to data their users can access. - Queries pass through validation, planning, optimization, and security stages before reaching the database. ## Engineer-Facing Data Explorer - The Data Explorer provides direct access to the same graph without an AI agent. - Engineers can use it to: - Investigate incidents - Trace dependencies across services - Diagnose recurring CI failures - GitLab positions it as a way to answer open-ended system questions in seconds rather than reconstructing the answer manually across multiple tools. GitLab Orbit is best suited to organizations where code, CI/CD, security, and ownership data are spread across large repositories or many projects. Its main recommendation is to use one permission-aware graph as shared context for both AI agents and engineers, rather than relying on repository search or disconnected tool calls.

Read original(opens in new tab)
gitlab3 min readCurated summary

GitLab: Built for the agentic engineering era

GitLab argues that AI coding only becomes truly “agentic engineering” when paired with infrastructure built for machine-scale concurrency, lifecycle context, and enterprise governance. At GitLab Transcend, it announced new source control, context, security, orchestration, and purchasing capabilities designed to let agents work faster without sacrificing control. The overall goal is to convert rapid AI-generated development into reliable business value rather than unmanaged complexity. ## The challenge: speed without control - Research across more than 1,500 developers and technology leaders found: - 91% of organizations use at least two AI coding tools. - 54% use three or more. - Some customer codebases are growing by as much as five times per year. - Fragmented development lifecycles create several problems: - Human-scale source control systems struggle with thousands of concurrent agents. - Agents lack context about dependencies, deployments, and production behavior. - Rapidly changing code is difficult to govern. - Fixed contracts make AI adoption difficult to forecast. - 73% of respondents worry about maintaining AI-generated code, while only 21% see productivity improvements across the full SDLC. ## GitLab’s agentic infrastructure model GitLab presents its platform as four coordinated systems: - **Motor system:** Source control, pipelines, and deployments that execute work. - **Nervous system:** Context that helps agents and humans make informed decisions. - **Immune system:** Security, governance, identity, policy, audit, and approvals. - **Orchestration system:** GitLab Duo Agent Platform, which coordinates work across the lifecycle. The company says these systems operate consistently whether work is performed by a developer or an agent. ## Next-generation source control for agent concurrency Git’s traditional workflow creates bottlenecks when every developer runs hundreds of agents: - Agents repeatedly clone repositories even when they need only one file. - Thousands of simultaneous sessions can overwhelm a human-oriented backend. - Shared accounts and branches make it difficult to isolate, audit, or discard agent work. GitLab’s next-generation SCM, currently in private beta, retains Git protocol compatibility while redesigning the backend and interfaces for agents. It is intended to support thousands of parallel agents working safely across repositories. Early internal tests reported: - Up to 2× fewer tokens - Up to 50× faster wall-clock execution - Up to 1,000× less network traffic ## GitLab Orbit: lifecycle context for agents Agents often understand the code they modify but not the broader software lifecycle, causing wasted iterations, hallucinations, and incorrect work across large or multiple repositories. GitLab Orbit, in public beta, provides a continuously updated context graph connecting: - Code - Work items - Pipelines - Deployments - Production signals This gives agents and engineers a shared source of truth. GitLab reports that Orbit-grounded agents achieved up to 11× faster responses, 4.5× better cost efficiency, and 45× fewer hallucinations in early testing. Compare the Market’s testing on 79 merge requests found that graph-grounded agents placed inline review comments correctly 69.6% of the time, compared with 57.7% for a conventional RAG approach. ## Governance, orchestration, and purchasing GitLab also announced: - **Agents for security and governance for agents**, covering identity, policy, auditing, and approval of agent actions, in private beta. - **GitLab Duo Agent Platform**, generally available since January, allowing agents to pick up issues, review code, and fix pipelines. - **GitLab Flex**, a purchasing model intended to accommodate the unpredictable pace of AI adoption. - A Transcend hackathon inviting developers to build agents and workflows using Orbit. GitLab’s practical recommendation is not to slow down AI-assisted development, but to pair it with dedicated infrastructure for concurrency, full-lifecycle context, and enforceable governance.

Read original(opens in new tab)
gitlab2 min readCurated summary

Mythos-class Claude Fable 5 arrives on GitLab Duo Agent Platform

Claude Fable 5, Anthropic’s Mythos-class model, is now available through GitLab Duo Agent Platform across all tiers and deployment models. The post presents it as a major step beyond incremental model improvements, emphasizing stronger first-attempt accuracy, sustained autonomous workflows, and better code review and incident analysis. Its main conclusion is that teams should apply it to complex, previously difficult engineering problems rather than routine tasks. ## More Accurate First-Pass Results - Produces more correct implementations for complex, well-defined problems with fewer iterations. - Reduces back-and-forth in Duo Agentic Chat. - Performs especially well on: - Multi-file refactoring - Incident investigation - Infrastructure-as-code definitions - Interprets technical images, web applications, and detailed screenshots more accurately while often using fewer output tokens. ## Longer and More Reliable Agent Workflows - Sustains goal-directed work across extended, multi-day runs and millions of tokens. - Maintains instructions and task focus without frequent manual checkpoints or re-prompting. - Uses verification loops to identify and correct its own mistakes. - Handles parallel sub-agents more reliably across multiple repositories or services. - Reduces the amount of human oversight required per agent run, allowing teams to review results asynchronously. ## Improved Bug Detection and Incident Response - Provides higher bug-finding recall than previous models. - Improves outage triage, root-cause analysis, and repository-history investigation. - Finds deeper code-path issues and edge cases during merge request reviews. - Produces more actionable review comments instead of generic feedback. - Helps reduce production defects and improve mean time to resolution. ## Recommended Use Cases - The post recommends testing the model on difficult, unsolved engineering problems rather than routine work. - Suggested applications include: - Complex multi-file refactors - Production incident investigations - Implementations developers would normally write manually - Teams should allow agents to scope work, ask clarifying questions, and execute multi-step solutions. Claude Fable 5 became available on GitLab Duo Agent Platform on June 9, 2026. Teams can access it through a free trial, the GitLab free tier, or included GitLab Credits for Premium and Ultimate subscribers.

Read original(opens in new tab)
kakao3 min readCurated summary

Key Players in the Agentic AI Ecosystem: MCP Player 10 Wraps Up, and What’s Next!

Kakao’s first MCP Player 10 competition showcased how developers are using Model Context Protocol (MCP) to build practical agentic AI services. More than 150 teams participated, and ten finalists were selected for solutions addressing childcare, startup support, culture, gaming, legal research, and safety. Kakao plans to expand this ecosystem through the upcoming Agentic Player 10 competition and deeper integration with Kakao Tools. ## The MCP Player 10 Competition - The competition ran from December 19, 2025, to January 18, 2026, on Kakao’s PlayMCP open platform. - It emphasized: - Creativity - Everyday usefulness - Technical stability - The goal was to encourage developers to create MCP servers that solve real-world problems with AI. - Ten teams were selected after internal evaluation and received a share of 21 million won in support funding, along with opportunities to collaborate with Kakao. ## Award-Winning MCP Services ### 어린이ZIP: AI Assistant for Childcare Teachers - Automates administrative work for daycare and kindergarten teachers. - Analyzes uploaded activity photos to generate drafts of parent notices and childcare journals. - Remembers child-specific details such as allergies and pickup arrangements. - Produces personalized responses in a warm, professional tone. ### SeedUp: Startup Support-Program Research - Collects and analyzes fragmented government startup-support announcements. - Summarizes eligibility requirements and relevant opportunities. - Helps founders develop application strategies. - Supports natural-language requests such as finding weekly deadlines or analyzing an uploaded announcement. ### Other Selected Services - **공유 비밀의 방:** An anonymous platform for sharing and empathizing with personal stories and AI conversations. - **바우만 16 안티에이징솔루션:** Recommends skincare routines using the Baumann 16 skin-type classification, cosmetic ingredient data, and skin pH analysis. - **아라드도우미:** A Dungeon & Fighter assistant using RAG and Vision AI to analyze patch notes, item trends, and optimized character builds. - **키즈허브:** Aggregates public data such as emergency-room availability, childcare waiting lists, and child-development information. - **택배추적기:** Combines package tracking with AI-based detection of smishing URLs in delivery-related messages. - **ArtBridge:** Recommends performances and exhibitions from approximately 200,000 records across nine cultural categories, using location, budget, and preferences. - **KidSafe:** Detects harmful language and emotional-crisis signals in children’s chatbot conversations, escalating serious cases to guardians or professional resources. - **LexiLink_ko:** Searches and organizes statutes, court precedents, and administrative interpretations through natural-language queries. All ten MCP servers are now officially available through the PlayMCP platform. ## PlayMCP’s Future Direction - PlayMCP will remain a developer-focused environment for building and distributing MCP servers. - Kakao Tools, available through ChatGPT for Kakao, will focus on helping general users experience MCP-based services. - Kakao plans to connect the two platforms more closely. - Kakao is considering managed infrastructure, including: - Kakao Cloud-based server support - Automated deployment - Greater operational responsibility for MCP service stability - PlayMCP may also support richer in-app interfaces through JSON-based widgets, similar to those already available in ChatGPT for Kakao. ## The Next Competition: Agentic Player 10 Kakao announced a second competition, Agentic Player 10, designed to connect developer-created agents with Kakao Tools and expose them to a broader audience. The program is positioned as an opportunity for startups and aspiring founders to test their services with real users and potentially bring their agents into KakaoTalk. Developers interested in building practical AI agents are encouraged to use PlayMCP and participate in Agentic Player 10 as the next step in Kakao’s expanding agentic AI ecosystem.

Read original(opens in new tab)
aws2 min readCurated summary

Try the new console experience in Amazon Bedrock, optimized for Anthropic- and OpenAI-compatible APIs | Amazon Web Services

Amazon Bedrock introduces a refreshed console centered on the `bedrock-mantle` inference engine, which supports Anthropic Messages, OpenAI Responses, and OpenAI Chat Completions APIs. The experience is designed to streamline model discovery, evaluation, application development, and production setup for GPT, Claude, and open-weight models. It complements the existing console, which remains available for features such as Agents, Knowledge Bases, Guardrails, fine-tuning, and `bedrock-runtime` APIs. ## Model Catalog and Comparison - Browse supported models in a unified catalog. - Compare up to three models by: - Capabilities and modalities - Context window and token limits - Pricing and input/output costs - Service quotas - Regional availability - Use side-by-side evaluations with identical prompts to compare model responses. ## Project-Based Workflow - Create projects that organize model assignments, evaluations, API keys, and application setup. - The project dashboard displays: - Inference requests and errors over selected date ranges - Recently used models - Total token usage - Tokens per minute - Requests per minute - Tokens per inference request - These metrics can guide model selection, prompt optimization, and workload consistency. ## Application Setup and Live Documentation - The console provides project-specific setup instructions for Anthropic and OpenAI SDKs. - Developers can select an SDK, programming language, and authentication method. - It generates terminal commands, `.env` configuration, and sample requests for quick testing. - Live API documentation automatically inserts the project’s model ID, Region, `bedrock-mantle` endpoint, and API key reference. - Documentation updates automatically when project models or settings change. ## AI Coding Agent Integration - Projects can connect coding agents such as Claude Code, Cline, Codex, Cursor, and OpenCode. - Setup instructions cover: - Installing the selected agent - Using AWS IAM credentials or Bedrock API keys - Configuring environment variables - Routing agent requests through Bedrock ## Availability The new console is available in Regions offering `bedrock-mantle`, including locations in the United States, Asia Pacific, Europe, and South America. Users can access it through the existing Bedrock console by selecting **Try the Bedrock Mantle Console**, while the traditional console remains available for fully managed Bedrock capabilities. Developers building with Anthropic- or OpenAI-compatible APIs can use the new console to move from model evaluation to application testing and deployment with less manual configuration.

Read original(opens in new tab)
toss4 min readCurated summary

How the Toss Team Faces the AI Wave: AI Surf Day

Toss created **AI Surf Day**, a dedicated weekly time for employees to experiment with AI, share lessons, and redesign their workflows. Running on Fridays from April through June, the initiative aims to reduce the AI gap across technical and nontechnical roles by making experimentation collaborative and accessible. Its broader conclusion is that successful AI transformation depends less on formal programs than on culture, time, and people who actively share what they learn. ## AI Surf Day’s Purpose - Employees focus on their core work Monday through Thursday and reserve Friday for AI experimentation and practical application. - The program addresses anxiety and knowledge gaps, especially among nondevelopers who may struggle to identify useful AI information or find time to learn it. - Its concept comes from Jon Kabat-Zinn’s phrase: “You can’t stop the waves, but you can learn to surf.” - The goal is to help Toss become a company that works with AI as a foundation, not merely a workplace where individuals use AI tools. ## AI Surf Club - Employees can create or join informal groups focused on AI topics; roughly 200 clubs were formed at launch. - An **AI Antipattern Study** focused on failures and mistakes, turning participants’ experiences into a practical guide for avoiding common problems. - An **LLM Wiki** group explored how to organize scattered organizational knowledge across data engineering, machine learning, and business teams. - A beginner-focused “Step 0” group helped employees overcome basic technical barriers, such as installing agent tools and asking questions they felt were too fundamental. - A customer-protection team built an external-complaint monitoring portal in one month, along with automation for complaint-response drafts and classification. - A marketing team divided AI work into roles such as: - **Builder:** creates AI-powered tools and workflows - **Curator:** collects useful examples and resources - **Operator:** applies AI to repetitive work - **Scouter:** identifies new opportunities - The clubs emphasized reusable outputs and shared confidence, rather than isolated individual experimentation. ## AI Surf Weekly - Weekly sessions share successful internal AI applications, lessons learned, and current industry insights. - Toss connected employees with similar needs across different departments, enabling them to solve problems quickly by learning from existing internal examples. - Rather than prescribing specific tools, the program presents ideas and use cases that encourage employees to adapt solutions to their own work. - Examples included connecting a sales employee with an HR colleague who had built a similar tool, and pairing a marketer with a designer experienced in AI-powered automation. ## AI Surf Evangelists - Toss selected 142 employees across its affiliated companies and teams to promote AI adoption in their own organizations. - Evangelists were chosen through peer nominations, recognizing people who already shared useful discoveries and helped colleagues overcome AI-related obstacles. - Their responsibilities over three months include: - Reporting effective AI use cases - Sharing useful insights with colleagues - Hosting at least one meetup or workshop - Toss’s Culture team provides workshop templates and facilitation support. - Many teams have conducted workshops around redesigning their existing workflows with AI. - The program treats AI adoption as a team-level workflow redesign challenge, rather than simply measuring individual proficiency with AI tools. ## OpenAI Collaboration and Mini-Hackathon - Toss held a special AI Surf Day with OpenAI on May 15. - Hands-on sessions covered: - Codex-based development workflows for developers - ChatGPT Agent-based automation for nondevelopers - A 2.5-hour hackathon produced two notable projects: - An iOS workflow where Codex implements features, operates the simulator, tests the result, iterates on problems, and produces verification footage. - An agent that classifies thousands of daily Toss Place product records, sends reviewers links, and supports approval or rejection through an admin interface. - These projects demonstrated how AI can become a reusable agentic workflow rather than a one-time assistant. ## Culture Over Programs - Toss does not claim to have a fixed answer for managing AI’s rapid evolution. - The lasting value of AI Surf Day is the protected time for learning and experimentation, along with a culture where employees openly share results and failures. - Successful examples spread naturally across teams, while evangelist-led workshops translate experimentation into concrete changes in how work is performed. Organizations pursuing AI transformation can take a similar approach: create dedicated experimentation time, encourage peer-led learning, recognize existing champions, and focus on reusable workflow improvements rather than tool adoption alone.

Read original(opens in new tab)
datadog3 min readCurated summary

From single pull requests to full software packages: Detecting malicious code at scale

BewAIre evolved from a pull-request malware detector into a system for scanning dependency packages and upstream registries. Its core improvement is a two-stage pipeline: a cheap LLM filter handles routine changes, while a more capable agent investigates suspicious cases using external tools and repository context. This approach raised accuracy from 97.4% to 99.86%, eliminated false positives in a 690-diff sample, and reduced latency and cost through early exits. ## Expanding Beyond Pull Requests - Software supply-chain attacks increasingly compromise trusted dependencies such as axios, LiteLLM, and Mistral. - BewAIre initially focused on detecting malicious pull requests, identifying security testing, bug-bounty activity, and real attacks such as the Hackerbot campaign. - The team aimed to apply the same LLM-based detection to complete packages and package registries without sacrificing accuracy, latency, or predictable cost. ## Limits of Single-Pass LLM Evaluation - BewAIre began as a basic “LLM-as-judge” system that analyzed diffs through an inference API. - More capable reasoning models improved detection but increased costs. - Large diffs, especially dependency upgrades, challenged context-window limits. - Two changes addressed these limitations: - A filter-then-review escalation path. - Tool-enabled investigation allowing models to gather additional evidence. ## Two-Stage Filtering and Investigation - The filter phase: - Runs on every change using a fast, inexpensive model. - Uses straightforward prompts and diff chunking for large changes. - Produces a binary suspicious/benign decision. - Ends processing immediately when a change appears benign. - The investigation phase: - Runs only when the filter raises a concern. - Uses a stronger reasoning model in an agentic loop. - Can inspect commits, files, contributor histories, dependency metadata, and commit ranges through GitHub APIs. - Checks for reverted commits, typosquatting, suspicious contributor behavior, and dependency risks using sources such as osv.dev and Datadog SCA. ## Detecting Obfuscated Attacks - In the Hackerbot Claw example, the system identified a malicious filename containing shell command substitution. - A base64-encoded payload decoded to a `curl ... | bash` command that downloaded and executed remote code. - The investigation agent added useful context: - The contributor account was newly created, had no profile information, and had no followers. - The pull request had no reviews or approvals. - `${IFS}` obfuscation was used to evade security filters. - Combining code analysis with repository and author context made the final assessment more precise. ## Combining LLMs with Static Checks - The filter model could mistakenly treat Datadog-like typosquatting domains as legitimate without access to investigative tools. - BewAIre added preprocessing that extracts domains and compares them against a static list of known typosquatting variants. - This hybrid design improves reliability while avoiding the cost and nondeterminism of performing every check through a powerful LLM. ## Measured Results - Accuracy improved from 97.4% to 99.86% across 690 representative test diffs. - False positives fell from 17 to zero. - Most benign changes exit during the inexpensive filter stage. - Suspicious changes still receive deeper analysis, preserving broad coverage while controlling latency and cost. The practical recommendation is to combine inexpensive broad screening with selective, tool-driven investigation. Static security checks should complement LLM reasoning, especially for predictable threats such as domain typosquatting.

Read original(opens in new tab)
aws4 min readCurated summary

AWS Weekly Roundup: Claude Opus 4.8 on AWS, Aurora MySQL with Kiro Powers, and more (June 1, 2026) | Amazon Web Services

AWS’s latest roundup highlights a rapid shift toward AI-augmented software development, illustrated by workshops where 17 teams delivered nearly 20 use cases in two days. The centerpiece is Anthropic Claude Opus 4.8, now available through Amazon Bedrock and the Claude Platform on AWS, alongside tools that improve resilience, agentic search, migration analysis, database management, and desktop streaming. Together, these launches show AWS moving toward real-time, AI-assisted development and operations. ## AI-Driven Development and Claude Opus 4.8 - AI-DLC workshops are helping teams deliver software use cases at unprecedented speed, especially when combined with Claude Code on Amazon Bedrock. - Development roles are increasingly consolidating into smaller, AI-augmented teams. - AWS account teams are shifting from producing advisory documents to building solutions collaboratively with customers. - Claude Opus 4.8 is Anthropic’s most capable generally available model and is designed for: - Agentic coding and extended autonomous tasks - Long-document analysis and knowledge work - Deeper reasoning and error recovery - Maintaining context across lengthy coding sessions - On Amazon Bedrock, it includes AWS features such as Guardrails, Knowledge Bases, and data-residency controls. - The Claude Platform on AWS provides Anthropic’s native APIs with unified AWS billing. ## AWS Resilience Hub - The next-generation Resilience Hub provides a unified way to define resilience standards, assess applications, and demonstrate compliance. - Modular policies cover: - Service-level objectives - Multi-Availability Zone and multi-Region disaster recovery - Data recovery - Generative AI assessments align with AWS Well-Architected and Resilience Analysis Framework guidance. - DNS query-log analysis automatically discovers application dependencies. - AWS Organizations integration enables centralized, organization-wide resilience management. ## OpenSearch Serverless for Agentic AI - Amazon OpenSearch Serverless is now positioned as a managed search and vector engine for agent-based applications. - It scales from zero to thousands of requests per second and is approximately 20 times faster than the previous generation. - AWS claims up to 60% cost savings compared with peak-provisioned clusters. - New capabilities include GPU acceleration and dedicated `SEARCH` and `VECTORSEARCH` collection types. - OpenSearch Agent Skills integrate with Vercel, Kiro, Claude Code, and Cursor. ## AWS Transform Assessment and Modernization Tools - AWS Transform can build migration business cases and estimate total cost of ownership. - It accepts data from RVTools, CMDBs, AWS discovery tools, and third-party discovery platforms. - Users can model what-if scenarios involving regions, utilization, and service mappings for services such as EC2, FSx, S3, SQL Server on EC2, and virtual desktops. - Agentic Readiness Analysis and Modernization Analysis scan repositories in roughly 5–30 minutes. - Findings include severity levels, file-level evidence, and AWS-specific remediation recommendations. ## Aurora MySQL with Kiro Powers - Aurora MySQL now integrates with Kiro Powers, which provide curated MCP servers, steering files, and hooks. - Developers can use natural language for both: - Data-plane tasks such as queries and schema changes - Control-plane tasks such as cluster administration - The integration offers guidance for Serverless scaling, RDS-to-Aurora migrations, and replication. - Kiro generates the relevant API calls, SQL, and configuration for developer review before execution. - Installation is available through the Kiro IDE or website. ## Windows Desktop Streaming with WorkSpaces Applications - Amazon WorkSpaces Applications now supports bring-your-own-license Windows Desktop OS deployments. - Customers can stream complete Windows desktops and applications from dedicated AWS hardware. - BYOL removes operating-system fees, leaving compute and streaming infrastructure charges. - Eligible Microsoft 365 Apps for enterprise are supported. - Users receive a consistent experience across local and streamed desktops. ## Additional AWS News - AWS introduced its May 2026 cohort of AWS Heroes. - A new Vercel and AWS Databases integration allows provisioning Aurora PostgreSQL, DynamoDB, and Aurora DSQL through Vercel or v0. - The H0 hackathon offers $160,000 in prizes for applications built with this stack. - AWS GovCloud customers now receive 24/7 support from US-based, US-citizen engineers automatically, without opting in. AWS’s direction is clear: combine capable AI agents with managed infrastructure, developer tools, and operational automation. Teams evaluating these services should focus on practical agentic use cases while retaining review and governance for generated code, infrastructure changes, and database operations.

Read original(opens in new tab)
aws2 min readCurated summary

Introducing the next generation of Amazon OpenSearch Serverless for building your agentic AI applications | Amazon Web Services

Amazon’s next-generation OpenSearch Serverless is a managed search and vector engine optimized for agentic AI applications. It scales from zero to thousands of requests per second, creates resources in seconds, and can reduce costs by up to 60% compared with clusters provisioned for peak demand. The release is generally available across supported AWS commercial Regions and integrates with tools such as Vercel, Kiro, Claude Code, and Cursor. ## Elastic Scaling and Cost Optimization - Scales capacity up to 20 times faster than the previous generation. - Supports scale-to-zero when idle, minimizing compute costs. - Charges separately for compute through OpenSearch Compute Units (OCUs), storage in GB-month, and GPU acceleration where applicable. - Supports capacity limits for indexing and search, with minimum capacity set to zero and configurable maximums. ## Creating Next-Generation Collections - Collections can be created through the Amazon OpenSearch Service console, AWS CLI, or SDKs. - The console’s **Express create** option automatically applies default settings and matching security policies. - At launch, supported collection types are: - Full-text search (`SEARCH`) - Vector search (`VECTORSEARCH`) - Users who need the existing infrastructure can select the classic OpenSearch Serverless generation. - Collections inherit their generation from a parent collection group. Example CLI workflows create a next-generation collection group with standby replicas and then create a search collection within it. ## Integrations for Agent Development - Vercel users can create or connect OpenSearch Serverless collections directly from the Vercel console. - OpenSearch Agent Skills bring search-specific knowledge, best practices, and multi-step workflows into agents using Claude Code, Cursor, and Kiro. - Kiro’s OpenSearch Launchpad provides guided architecture planning for building search applications. ## Availability - The next generation is generally available in all AWS commercial Regions where OpenSearch Serverless is currently offered. - AWS recommends consulting the OpenSearch Serverless documentation and pricing information for configuration and cost details. The release is intended to let developers deploy production-ready search and vector backends quickly, while avoiding the infrastructure management and peak-capacity costs associated with provisioned OpenSearch clusters.

Read original(opens in new tab)