AI enablement, security, and control in one platform. The default for AI-native teams like Gusto, Lemonade, & Baseten.

NYC & SF
Joined September 2025
Runlayer retweeted
Today, we're launching the ability to say yes to Muse at work. People are giving Muse access to their company's most sensitive data & systems. Yet companies have no way to control this access. Many are blocking it. Others have had Muse go rogue, leaking company data, sending unauthorized emails, and more. Runlayer provides hundreds of secured connectors for Muse, governed by deterministic policies & runtime security models that you can control. Runlayer also detects when Muse is being used within company systems without governance, and alerts you. Teams get access to the most powerful personal agent. Companies maintain security and control. Win win.
32
27
13
239
71,417
my AI Engineer talk is finally online a bit outdated already but one thing will be probably always true - failed agent runs are your richest signal youtu.be/u-o0sW9nwmk?is=BcYS…
1
1
10
829
Runlayer retweeted
Your teammates have arrived.🤖 @runlayer is now on Slack. Build agents with their own identity, full company context, and governed access to your tools. One click and they’re ready to @mention, DM, and work like anyone else on the team. Explore: sforce.co/3VYP6A8
6
1
1
21
8,789
mcp is dead, long live mcp? collabed with opus to put together this 102 explainer. there's plenty of content on "what is mcp" not enough on MCP & context window i covered: - context bloat, and why it turned out to be a client problem - servers hiding all their tools behind search & execute - the "just use CLIs" take, shipped to a 5,000-person company - why boring standards win 0:00 - MCP is dead (again) 0:29 - The original sin: context bloat 0:53 - Plot twist: it was a client problem 1:23 - The meta-tool detour 1:56 - This year's hype: just use CLIs 2:37 - What MCP actually bought you 3:28 - Two-way street 3:50 - How standards win
3
6
1
29
2,052
Runlayer retweeted
Jake Moghtader from @runlayer about agent runs benchmarks, secuirty and mcp at @AgenticAIFdn 🇳🇱 Monitoring, observable agentic workloads and tracing are the topics.
2
1
5
443
In SF for the day reppin’ @runlayer at @browserbase Navigate. :)
1
27
601
Opinions on agentic engineering appear to be converging into two camps: "You should put a lot of planning up front, all the way down to program design, then let the agents cook", aka the @humanlayer_dev way. vs "Do a shit ton of investment in architecture/linters/LLM checks/automatic verification upfront, and then let agents rip. Garbage collect periodically", aka the @poteto way. I currently land somewhere in-between: - A bunch of research and planning up front, but skip program design unless I identify that a net-new abstraction will be needed, or I know I'm working on high-stakes/core code. - For "every day" stuff, I lean heavily on guardrails. - Frequent sampling of PRs that have been landing on main to spot problematic code that should've been caught by a guardrail. Add more guardrails to catch it, burn down the offenders. - Frequent sampling of hot spots in the codebase, to detect when human intervention is needed, e.g. an abstraction has grown out of control. Maybe I oughta build a heatmap visualization for this? - I also love @poteto 's take on the tier of guardrails (opinionated architecture > static analysis > tests > LLM checks)
11
6
3
114
15,806
Runlayer retweeted
so it seems like @runlayer CEO doesn't have an account here, but recently I stumbled upon something smart that he posted on his LinkedIn and I thought everyone will benefit from this here this Friday. think first
1
1
2
450
Runlayer retweeted
This is exactly what we enable our customers to do. Our process is basically Uber's on steroids. 1. We pair an FDE with your AI champion. Every rollout starts by embedding one of our forward-deployed engineers with the person on your team actually building agents 2. We see what's already running. A discovery scan maps every AI client, MCP, and shadow connector across the company. In almost every org, 3–5 MCPs drive 85%+ of agent traffic, so we know exactly what to build on. 3. You build agents with your team, live. Working sessions where your team drives. They build the agent in a local session (Claude Code, Codex), wire in your connectors, then use the platform to see what it did, audit the run, and iterate. We end this with a working agent, not a bad prototype. 4. The platform makes the good agents reusable. Build a skill privately, iterate on it, then share it org-wide and invoke it from Slack. Literally, one person's S-tier workflow becomes everyone's. 5. The platform also optimizes every run. An agent optimizer audits each run for tool usage, prompt quality, and model choice, right-sizing Opus down to Sonnet where it holds up. 6. Now (and only now) do we turn controls on. Never as a hard stop: start in alert mode, build the allow-list, flip to enforce once a better path exists. RBAC on every agent, full session visibility, nothing yanked. TL;DR is let the most AI-pilled experts go crazy, give them a platform, and share their agents and expertise with everyone else at the company. Everyone else learns from these experts. Using @Runlayer, we almost always find the biggest wins hiding in plain sight. They're with your most AI-forward engineers. But the best agents beyond that are hidden in the processes your SMEs know by heart. It should be dead simple for them to turn that process into an agent. That's who we enable to run on a golden path to AI adoption. xitter.cf/praveenTweets/status/2…
Agentic AI adoption is on fire at @Uber, and it's changing the way we build, not just in engineering, but across the entire company. Today, 99% of our engineers use AI tools. More than 70% of pull requests are attributed to local or cloud agents. And our engineers have built 2,500+ agent skills across the software development lifecycle. Those numbers are exciting, but they led us to a much bigger question: How do we bring agentic AI beyond engineering? Finance. Legal. Operations. Marketing. Customer Support. HR. Procurement. These functions run on complex workflows that are often manual, highly nuanced, and spread across dozens of systems. You can't automate them effectively by looking at process diagrams or documentation. You have to understand how the work actually gets done. So we created something called Agentic Pods. The idea is simple. We handpicked ~30 of our most AI-proficient engineers (people with deep knowledge of Uber's systems) and paired each of them with a domain expert from a business function. Then we gave every pod just two weeks. • Days 1 – 2: Shadow the expert. Observe every step. Document workflows. Ask questions. Build intuition. • Day 3: Prioritize opportunities based on scale, repetition, business impact, and data availability. • Days 4 – 5: Build a working agent alongside the person doing the job. • Days 6 – 9: Validate with several others performing the same work. Does it generalize? Does it actually make their job better? • Day 10: Ship. In just the past two months, we've run 16 Agentic Pods across 16 different business functions. • Capital allocation across 150 cities: 15 hours → 30 minutes. • Financial pacing reports: 2 days → 10 minutes. • Marketing web quality assurance: 2 weeks → 50 minutes. • Support workflow creation: 9,000 manual workflows → self-service automation. The productivity gains are impressive, but what surprised us most wasn't the speed. • It was how quickly engineers embedded in unfamiliar domains uncovered opportunities that had been hiding in plain sight. • The biggest wins rarely come from automating one task. They come from rethinking an entire workflow. Once you redesign the workflow around AI, you often eliminate handoffs, remove unnecessary approvals, replace legacy tooling, reduce vendor spend, and dramatically accelerate decision-making. • The workflow becomes the unit of automation - not the individual task. • The most impactful agent skills cut across teams, orgs, functions, tools, and systems. The biggest lesson? The best AI opportunities are rarely visible from the outside. You discover them by sitting next to the people doing the work, understanding every friction point, and building with them, not for them. We're now forming a dedicated team to scale this further and go deeper. They'll deeply understand the work, redesign it from the ground up, and use AI to fundamentally change how the business operates. It's exciting times!
7
7
210
50,419
Runlayer retweeted
Runlayer takes AI Engineer World's Fair in SF this week! Here's what's happening: - @rafalwilinski giving a talk on Self-Improving Agents, one of Runlayer's hottest new products, today at 12pm pt - Raffles for swag, including iPads & custom Nikes, at our booth. All you have to do is stop by (next to AWS & Microsoft) - Premier sponsor this year, so every attendee gets a lanyard with our logo. reminder that every company attending can become AI-native with @runlayer
1
3
18
1,765
Runlayer retweeted
Thanks to @FortuneMagazine @LilyMaeLazarus for the feature!
1
1
32
6,038
Runlayer retweeted
Today, we’re announcing Runlayer has raised $30M from Felicis and Khosla Ventures to help companies go all in on AI. Runlayer is the golden path for AI: enablement, security, and control in one platform. So, how does it give your team the right tools for AI? 🧵
157
104
99
820
812,533
Runlayer retweeted
The 3rd-most used agent at Runlayer creates a living graph of our entire company. We couldn't operate without it. How it works (bookmark this): - Pulls from meeting transcripts, publicly accessible emails, public Slack channels, Linear tickets, and GitHub commits on a daily basis - Reads this activity and spawns sub-agents to record it all - Generates a knowledge graph of the company's decisions, action items, blockers, and key updates - Inserts this into a living database that's constantly updating The core idea is to record Runlayer's core systems and activity across the graph. Then, synthesize that information to help with higher-level work. A few sub-agents we run using this context graph: - Product overview agent: updates a product overview page based on shipped work so it reflects what Runlayer offers, day-of, for GTM - Messaging agent: continuously updates a Notion page with core messaging it hears across sales calls that is resonating - Competitive battlecard agent: detects competitor mentions from sales calls, Slack, and emails, adds missing competitors, and updates battlecards with reasons they position themselves as better Now, we have a constantly-updating database which employees (and agents) can reference. We can learn from this memory layer to make decisions, prioritize features, and find out what repetitive tasks should become an agent. Runlayer gives our employees a golden path to build agents like these, and this is the direct result. Follow if you're interested in seeing more agents - I'll be publishing stuff like this every week. I'll probably post the top 2 next week.
1
3
31
2,992
Runlayer retweeted
You can't make an AI-native company by mandate. When you try, 5% of people run with AI. The other 95% hit the valley of despair, and give up. Buying Claude licenses is the first step, but it's a smoke screen. Your employees hit the valley of despair next. - They want to connect Claude to sensitive tools and systems. - They want to build and share skill files. - They want to build agents. That’s the part that gets hard. Adding Claude doesn't magically change your workflows. Companies succeed by making the right way to use AI the easy way. Concretely: 1. Right path: Golden path for every employee, not just power users 2. Right platform: enablement AND control in one platform. Security platforms stifle adoption. They're not built for actual usage. 3. Right choice: a platform used by actual AI-native companies, not laggards. This is how we designed @Runlayer. This is how AI-native customers like Gusto and Instacart use Runlayer. Those executives mandated AI usage, sure. They also gave every single employee a golden path.
2
1
14
3,219
Runlayer retweeted
Anthropic just shipped MCP Tunnels. @Runlayer supports them on day one, after months of close work with the @AnthropicAI team. The Anthropic tunnel carries Claude's MCP calls into your network. The Runlayer Gateway is where they land: one endpoint in front of every MCP server you run, applying identity, policy, security, and logging on every call.
5
8
1
68
7,621
Runlayer retweeted
"Who uses Runlayer at Gusto? Everybody." Legal, HR, finance, engineering and the executive team. "Take this data in Salesforce, send this Slack, draft this email, go!" One interface, one conversation. Works with whatever client they're in: Codex, Claude Code, take your pick. Once people see what's possible, they don't go back. Watch Mike Wittig, Gusto's CISO & CIO, break it down in 80 seconds. 👇
2
2
1
19
2,266
“MCP is dead” misses the point MCP isn’t about tools. It’s about OAuth If that seems pointless, you haven’t deployed anything beyond a demo
Thank god MCP is dead Just as useless of an idea as LLMs.txt was It's all dumb abstractions that AI doesn't need because AI's are as smart as humans so they can just use what was already there which is APIs
91
22
20
566
187,024
Runlayer retweeted
The MCP ecosystem is growing faster than any protocol I've seen.
Cursor now supports MCP Apps. Agents can render interactive UIs in your conversations.
2
1
17
5,054
Runlayer retweeted
If your team is running MCP through @runlayer, your meeting notes are ready.
1
5
1
22
7,248
Runlayer retweeted
Talked to an engineering leader at a $14B company. Nearly 1,000 repos containing AI skills and plugins. Two people approve all of them.
2
1
6
783