Relay AI Automation Startup Closes, Team Joins Google Chrome to Boost AI Workflows

Relay shuts down, team moves to Google Chrome

On August 16, 2026, Relay, the San Francisco‑based AI‑automation startup founded by Jacob Bank, announced it would cease operations. In a terse blog post, Bank revealed that the entire engineering staff has been hired by Google to work on the next generation of AI features inside Chrome.

What happened

Relay raised a $45 million Series B round in early 2025, promising to let users “orchestrate AI agents across apps with a single click.” The product launched a beta in late 2025, but adoption lagged behind expectations. After a strategic review, the leadership team decided to close the company and accept Google’s acquisition offer for the talent pool only—no IP or assets were transferred.

Bank’s statement summed up the move: “We have some really ambitious plans to help you work with AI in Chrome to get things done, and I’ll have more to share soon.” The team’s expertise in multi‑agent orchestration, natural‑language command parsing, and low‑latency cloud‑edge integration will now be applied to Chrome’s upcoming AI‑assistant layer.

Why it matters

Chrome commands over 65 % of global web traffic. Embedding AI automation directly into the browser could shift the development paradigm from server‑centric AI services to client‑side, on‑the‑fly workflows. For developers, this means:

• Instant access to AI agents without managing separate back‑ends.
• Reduced latency by leveraging Chrome’s V8 engine and upcoming WebGPU support.
• New extension APIs that expose Relay‑style orchestration primitives to any web app.

Google’s move also underscores a broader industry trend: big browsers are becoming the default platform for AI‑augmented productivity, competing with native desktop apps and cloud‑only services.

Implications for developers and founders

Developers building SaaS tools, internal dashboards, or developer‑focused utilities should start treating the browser as an AI runtime. Founders of early‑stage AI startups need to reassess whether a browser‑first strategy can give them a distribution advantage over native‑app or cloud‑only models.

Key takeaways:

• Watch Chrome’s roadmap. Google has promised a “Chrome AI” beta by Q1 2027. Early adopters who prototype against the new APIs will gain a first‑mover edge.
• Re‑architect existing integrations. If your product currently calls external AI endpoints, consider moving logic into a Chrome extension or progressive web app (PWA) to cut round‑trip time.
• Leverage open standards. The Web AI Working Group is drafting WebAgent and AI‑Orchestrator specs. Aligning with these standards will protect you from vendor lock‑in.

What you should do now

1. Experiment with Chrome’s preview APIs. Sign up for the Chrome Developer Program and start building a simple “AI‑to‑clipboard” extension that uses the upcoming chrome.ai.runAgent method.

2. Audit your data flow. Identify latency‑sensitive parts of your stack that could benefit from client‑side execution. Move those to the browser where possible.

3. Update your roadmap. If you were planning a native desktop client for AI‑driven automation, reconsider whether a PWA could deliver comparable UX with lower maintenance overhead.

4. Network with the former Relay team. Google has opened a public forum for early collaborators. Engaging now can give you early access to design docs and sample code.

Timeline of key events

For developers, the Relay story is a reminder that AI tooling is rapidly moving from niche SaaS products to the core of the web platform. The next wave of productivity will be built on browser‑native agents, and the teams that adapt now will shape that future.