1Password launches Credential Broker to hand credentials to CI, workloads, and AI agents

What changed: 1Password announced a private‑beta Credential Broker that brokers credentials, tokens, and federated access from 1Password into trusted requesters (starting with GitHub Actions) so secrets are delivered at time of use instead of being copied into repos, environment files, or pipelines.

Why it matters: For builders and operators, this replaces brittle long‑lived secrets in code and CI with an auditable delivery flow for humans, services, and agents — lowering leak surface area and making it practical to let agentic workflows (and GitHub Actions) fetch short‑lived credentials when they need them.

Try/watch: If you run agentic automation that needs service tokens or cloud creds, join the private beta and test a brokered workflow in a sandbox repo; watch for integration support beyond GitHub Actions (broader workload identity) and how delivery latency and rotation policies affect agent run times.

AWS puts a FinOps Agent and agent observability tools into preview

What changed: AWS published a June 15 roundup that includes an AWS FinOps Agent preview (a scheduled agent that answers cost questions, surfaces optimizations, opens Jira tickets, and investigates cost anomalies) and announces OpenSearch Service support for agent‑friendly MCP Apps for logs, traces, metrics, and agent observability.

Why it matters: Founders and engineering leads can now prototype automated cost‑management workflows that run as agents (not just dashboards). That matters because agentic systems can create continuous, high‑frequency model and tool calls that drive surprise spend — the FinOps Agent plus agent observability tools give you a way to detect, investigate, and automate fixes instead of discovering cost problems manually.

Try/watch: Add budget and anomaly alerts to a dev account and connect an agentic playbook that triages and files tickets; monitor how many automated investigations the agent runs and whether they introduce new API or model calls that themselves need FinOps controls. Also watch model-routing and per‑task attribution features: without per-call cost attribution, agent loops will still surprise you.

Cast AI’s Kimchi Coding adds MiniMax M3 to its autonomous coding agent

What changed: Cast AI announced that Kimchi Coding — an autonomous, multi‑model coding agent — now offers access to MiniMax M3 (rolled out to early access on June 15), and that Kimchi’s orchestrator routes tasks to the best‑fit model with a FinOps dashboard to stop runaway agent loops.

Why it matters: For small teams and startups that run coding agents from the terminal or CI, this is a practical example of model orchestration: reserve frontier models for the hardest steps while cheaper models handle the bulk, and use a real‑time token FinOps view to tie model choices to dollars and teams. That reduces cost and gives predictable developer experience when agents perform long‑horizon code tasks.

Try/watch: If you use coding agents in CI or local developer tooling, test Kimchi in shadow mode (observe-only) to compare output quality and cost versus your current model mix; watch for how well its orchestrator categorizes task complexity and whether the FinOps caps prevent useful retries in high‑latency codeflows.