Enterprise AI platforms are only as capable as the runtimes they execute.
If the runtime doesn't expose audit events, traces, policy decisions, identity, workflow context, and security controls, every platform has to rebuild them.
Forge is building those runtime primitives.
Forge v0.16.0 extends the runtime with AWS Bedrock support, platform admission hooks, distributed trace propagation, workflow correlation, and enterprise security controls.
🚀 Forge v0.16.0
☁️ AWS Bedrock Support — native SigV4 outbound authentication for Anthropic and OpenAI-compatible endpoints 🛡️ Platform Admission Hooks — enable AI platforms to enforce quotas, budgets, and execution policies before an agent runs 🔗 End-to-End Trace Propagation — subprocesses and external tools automatically join the same distributed trace 📊 Expanded OpenTelemetry — authentication, scheduling, channel delivery, and admission are instrumented out of the box 🔄 Workflow Correlation — separate workflow definitions from executions for complete lifecycle visibility 🌐 Automatic Workflow Context Propagation — securely propagate workflow identity across trusted internal services ✏️ Skill Builder Edit Mode — iterate on existing skills directly from the web dashboard 🔐 Unified Audit & Redaction Pipeline — one consistent security model across audit logs, guardrails, and traces
The goal isn't to build another agent framework.
It's to provide the runtime capabilities that enterprise AI platforms need to operate agents securely, observe them end to end, enforce policy, integrate with enterprise infrastructure, and govern them at scale.
That's what Forge is building.
Full release notes → https://t.co/B4BzxCYsfY
#Forge #EnterpriseAI #AIAgents #AgentRuntime #OpenTelemetry #AmazonBedrock #Kubernetes #OpenSource
Most AI agent frameworks stop at inference.
Enterprise agents need much more:
🛡️ Security controls that can be audited
📅 Scheduling that survives process restarts
🏢 Multi-tenant governance
🔍 Compliance evidence for every decision
☸️ Native cloud infrastructure integration
That's what Forge v0.15.0 delivers.
Forge v0.15.0 🚀
☸️ Kubernetes-Native Scheduling — deploy agent schedules as native Kubernetes CronJobs
🔐 End-to-End Guardrails Audit — every input, context, tool, output, and stream decision is now auditable
📡 OpenTelemetry Guardrail Spans — blocked prompts and policy violations show up directly in traces
🏢 Multi-Tenant Audit Stamping — org_id, workspace_id, entity_id, and entity_type on every audit event
🔍 SIEM-Ready Governance — filter audit streams by organization, workspace, or agent without joins
🤖 forge auth — token management and Kubernetes secret generation built in
📚 Forge as Go Modules — embed forge-core, forge-skills, and forge-plugins directly into your platform
One of the biggest additions:
Forge agents can now be scheduled using native Kubernetes CronJobs.
No custom scheduler.
No database dependency.
No timing drift.
The Kubernetes control plane serves as the scheduler, etcd as the persistence layer, and Forge automatically generates CronJobs, RBAC, and deployment artifacts.
Enterprise agents need governance as much as intelligence.
Forge now provides out-of-the-box auditability across guardrails, traces, tenants, workspaces, and agents.
Full release notes → https://t.co/3BkG2tSdfE
#Kubernetes #AIAgents #AgentOps #OpenSource #OpenTelemetry #Security #PlatformEngineering
Enterprise AI agents can’t be governed with logs alone.
When an agent makes 10 LLM calls, invokes 5 tools, talks to 3 other agents, and takes action in production, you need to answer:
🔍 Why did it do that?
💰 What did it cost?
🛡️ Was it compliant?
📊 How did it perform?
🔗 Which workflow triggered it?
That’s why distributed tracing isn’t observability theater—it’s the foundation for enterprise agent governance.
Forge v0.14.0 🚀
📡 End-to-End OpenTelemetry Tracing for AI Agents
🔗 Multi-Agent A2A flows appear as a single distributed trace
🤖 Automatic tracing for LLM calls, tool execution, and outbound APIs
📊 GenAI semantic conventions for token usage, model attribution, and cost analysis
🛡️ Audit ↔ Trace correlation with trace_id and span_id on every audit event
🏛️ Governance-ready visibility for security, compliance, evaluations, and operations
☸️ OTLP collector auto-added to egress policy and Kubernetes deployments
⚡ Works with Tempo, Jaeger, Honeycomb, Datadog, Grafana Cloud, and any OTLP backend
The best part?
No manual instrumentation.
Forge agents are automatically instrumented end-to-end—from the inbound A2A request to every model call, tool invocation, downstream agent hop, and external API request.
One trace. Complete lineage. Production ready.
45 files changed. 5.5k+ lines added. 8 issues closed.
Full release notes → https://t.co/7Zpgqado9v
#OpenTelemetry #A2A #AIAgents #AgentOps #Observability #OpenSource #useforge #initializ
a .map file in npm just exposed Claude Code's entire source code.1,809 TypeScript files. 500K+ lines. 89 feature flags. anti-distillation countermeasures. internal model codenames.what's inside is way bigger than the leak itself 🧵