531 posts tagged with "AI agents"
AI agents and autonomous systems
One Token, Seven Tools, Total Access: What a Czech Community's Coolify MCP Bridge Teaches About Agent-Operated Self-Hosting
A Czech community's 200-line MCP bridge lets AI agents operate Coolify apps from AnythingLLM behind a single bearer token, no permission model, and TLS verification off. A code-level inventory of its seven tools and the guardrail checklist that separates homelab experiments from tenant-ready agent platforms.
Your AI Coding Assistant Is Outpacing Your Pipeline: What DORA's Numbers Say About Platforms
Three years of DORA research agree: AI tools make developers faster and delivery less stable, and platform quality decides which effect wins. The numbers behind the amplifier finding and what they mean for teams running their own PaaS.
Netlify Calls the Model for You: What Zero-Key Agent Runners Teach Self-Hosted MCP Servers About Auth
Netlify's Agent Runners remove model API keys by billing inference through its AI Gateway; why a self-hosted deploy-from-chat platform should answer with tenant-held keys plus short-lived OAuth 2.1 agent credentials instead of rebuilding the broker.
One Control Plane, Four Operators: What OpenChoreo's MCP Bet Teaches Self-Hosted PaaS Builders
OpenChoreo 1.0 treats AI agents as first-class platform consumers through MCP servers on a single Kubernetes system of record. A four-surface replay plus an identity, dependency-graph, policy, and audit-trail checklist for letting agents investigate — and eventually change — deployments.
Harvest Now, Decrypt Later Comes for Your MCP Server: Why Agent Deploy Calls Are Worth Storing
A June 2026 executive order made harvest-now-decrypt-later federal policy — and the ciphertext most worth storing is your agent's deploy calls. A three-layer exposure audit plus a concrete checklist for hybrid post-quantum key exchange on an infra MCP server's own transport.
No Human Typed This Deploy: What Claude's Cron-Triggered Agents Demand From Your MCP Auth Story
Anthropic's June 2026 scheduled deployments let agents wake on a cron schedule, pull vault credentials, and ship with no human watching. Here is the six-rule auth checklist — scoped per-run grants, platform-written audit trails, blast-radius limits — a deploy-from-chat MCP surface needs before a timer gets deploy rights.
Every PaaS Now Speaks MCP: What Render, Fly, and Railway's Agent Bet Means for Whoever Owns the Server
In six weeks of summer 2026, Render, Fly.io, and Railway all shipped agent surfaces — OAuth MCP servers, disposable computers, chat plugins. A side-by-side inventory of what each actually exposes, the five things agent-operated deploys require, and the case for an open MCP server on machines you own.
The Hybrid-Platform Trap: Why Bolting AI Agents Onto Your Dev Platform Breaks
35% of organizations run AI tooling bolted onto a developer platform designed for humans. A five-row audit of what breaks when agents operate the sidecar — auth, status, rollback, guardrails — and the API-first contract that fixes it.
Keep Secrets Out of Your AI Agents: Credential Gateways, Short-Lived Tokens, and the Leak That Should Be Impossible
A prompt-injected agent leaks whatever secrets it can see — so stop letting it see them. How credential gateways, short-lived OIDC tokens, and Vault-backed brokers make agent access provable and revocable.