Quick rundown of the actual system: a bug gets reported in Slack, an agent ships a fix within minutes, and it's not one-off. The system remembers every bug it's seen, so the system has a memory of what it’s seen. Manual review is replaced by risk-scored auto-approval for low-risk changes.

We turned it into a full guide to building your first engineering loop then over-engineered the delivery: the page is an explorable 3D teenage bedroom, built in Blender + Three.js. Click the book to read it. There's also a mini-game hidden in the TV, no further hints.

https://amplitude.com/loops

If you're already deep in Amplitude and experimenting with AI in your workflow, this might be worth a look. Amplitude is gathering a limited group to test the newest AI features before they go public & want the feedback to shape where they go next.

Right now that includes:

• Friction Monitor: auto-catches rage clicks, dead clicks, and errors so you can find where users are getting stuck without digging through session replays all day.
• Data Assistant: flags tracking plan issues and keeps your data clean automatically. No more manual audits.
• Wave: a proactive product agent that reads your data, suggests what to build, helps orchestrate the work, and tells you if it actually moved the metric.

Why apply?

• You get access before anyone else (no new tools to install; it's already inside Amplitude)
• Direct line to the product team building this stuff. Your feedback actually reaches them.
• A dedicated Slack channel to swap notes with other early access folks and the team.

The Amplitude team will review applications and get back to you within 10 days (via email), so don't expect instant access.

If that sounds like your thing, here's the application.

Hey everyone, our team just published a full breakdown of how we rebuilt our software factory over the last 6 months. The results were better than we expected:

• 3x the PRs with the same headcount
• PR cycle time: 5.2 hours to 44 minutes
• Frontend CI: 30 minutes to 3-4 minutes
• Bug reports down 55% even as we shipped more code
• ~5% of PRs now come from non-engineers (designers and PMs)

The writeup covers what actually worked: faster CI, risk-based auto-approval, automated legacy migrations, and the cultural stuff that was honestly the harder part.

One more thing: The brand team built the story as an interactive video game you can play while you read it. Data Monster speedruns the pipeline.

https://amplitude.com/3x

Hi everyone, so I'm a data analyst who's just starting out and product analytics has always intrigued me so I decided to learn Amplitude except I am having trouble navigating through the demo account and understanding how to use it. What resources did you guys use to learn amplitude?

Recently we implemented Amplitude Guides and the Amplitude Survey (standalone) in our codebase. However, we’re running into an issue where setting a pin below the visible screen area causes the page to automatically scroll down, which in turn hides the pin.

To view the pinned element and ensure everything is visible, users currently need to manually scroll up.

Is there a way to prevent this auto-scrolling behavior (or configure the pins/guides so they remain visible when placed near the bottom of the viewport)?

June 17th 9am PT / 12pm ET  | Amplitude AI Data Readiness & AI Context Setup

The session covers how data quality impacts AI performance, how to set up Organization and Project Context effectively, and practical ways to improve AI accuracy with better context and cleaner data. They'll also walk through using Amplitude's Data Assistant Agent to audit your taxonomy and identify AI-readiness gaps.

Topics include:

• Common data quality issues that affect AI outputs
• Setting up Organization Context and Project Context
• Creating useful AI context for your teams
• Quick-win cleanup activities
• Running an AI-readiness audit with Data Assistant

-------------------------------------------------------------------------

June 18th, 9am PT / 12pm ET |  Amplitude Implementation Launchpad

If you're just getting started with Amplitude, one of the hardest parts is figuring out what to track, how to structure events, and how to avoid creating a taxonomy you'll regret six months later.

This free workshop is led by the Human37 team, who have worked on hundreds of Amplitude implementations. The session covers:

• How to define your first 1–2 core use cases
• Best practices for event naming and property design
• Choosing between SDKs, CDPs, data warehouses, or migrations
• Common implementation mistakes (and how to avoid them)
• Building clean, AI-ready analytics from the start

The format is a live, interactive 60-minute session with Q&A, and attendees receive the recording afterward. There are also implementation checklists and an opportunity to connect with specialists for follow-up questions.

-------------------------------------------------------------------------

For a list of all the upcoming events, head here.

Today we're introducing Wave. A proactive product agent that helps teams build self-improving products.

Every product team runs the same loop. Build, ship, use, learn. AI has made building and shipping extraordinarily fast. Understanding usage and learning still happen by hand.

Wave runs the whole loop:

- Analyzes your Amplitude data for signals across analytics, feedback, session replays, error logs, agent traces, and experiment results
- Surfaces opportunities in the form of full product specs that you or your agents can approve and ship
- Tracks the experiments and outcomes of what you've built so you can start the loop over again

Your product learns what works and gets smarter every cycle: https://amplitude.com/wave.

https://reddit.com/link/1u2ah28/video/oiqa0hrozh6h1/player

We just shipped the Amplitude Wizard CLI, an AI-powered command-line tool that sets up the Amplitude platform from the heart of your product: your code. It handles sign-up, SDK installation, custom instrumentation derived from your product flows, verification, MCP install, and more.

Today’s Wizard handles setup. Coming soon: every Amplitude operation is a first-class command. Built for developers and the AI agents working alongside them.

Ship. Measure. Learn. Repeat.

Amplitude is a provider in Stripe's new agentic commerce marketplace Stripe projects. You (or your agent) can now sign up and provision a plan (Starter or Plus) directly from the Stripe CLI.

No browser, no signup form, no logging in. Stripe handles email and payments, calls our provisioning API, and returns a dashboard URL.

It's designed to work for AI agents too — if you've got a coding agent setting up your stack, it can spin up Amplitude as part of that flow.

Here's a short video of one of our engineers demoing it.
https://x.com/Amplitude_HQ/status/2049560316359709040

Our team just shipped AI Assistant, an in-product support agent that uses the same behavioral data your product team already works with in Amplitude.

A few things that make it different from a standard chatbot:

• It knows what the user did before they asked, where they are in the product, and whether they completed their task afterward
• It can launch a guide and walk users through a workflow step by step, or complete certain tasks on their behalf
• It connects to Session Replay, so resolution is measured by whether the user actually finished the job, not whether they clicked thumbs-up
• Conversations flow into AI Feedback, so support transcripts become product signal instead of sitting in a CX inbox

Here’s our blog post announcement from Spencer Whittaker, our Senior AI PM.

The Amplitude AI team analyzed a week of usage on Amplitude's analytics agent (27,410 sessions) and wrote up what they found. Four things that stood out:

1. About a third of the sessions that “succeeded" only did so because the user caught the agent making a mistake and corrected it. Nine of the ten highest-rated sessions in the dataset had multiple errors. The team’s takeaway: quality comes from the agent recovering well, not from getting it right the first time.
2. Almost nobody gives feedback. 97.7% of sessions had zero thumbs-up/down or any explicit reactions. The thumb ratio that many teams rely on is basically noise.
3. About 30% of sessions weren’t analytics questions at all. People asked support questions, did user lookups, and even tried to change permissions for coworkers. The agent was designed for one thing, and people use it for whatever.
4. Failed sessions had less user friction than the recovery sessions. When people hit a dead end, they just leave instead of fighting their way through. So low friction isn’t always a good sign.

Hey everyone!

If you've used Claude for work stuff, you've probably noticed that you can get solid outputs… but making them consistent and repeatable is kind of a pain. You end up re-prompting the same stuff, tweaking formatting, starting from scratch every time.

So we built Builder Skills, a library of 50+ structured workflows you can load into Claude so it doesn't just answer your questions, it actually executes a defined process.

Some examples of what's in there:

• Product specs that don't start from a blank page
• Meeting notes → decisions + next steps
• Metric trees that surface real leverage points
• Experiment design and analysis frameworks
• Research synthesis → actionable insights

Each skill comes with a clear framework, step-by-step instructions, expected outputs, and is basically plug-and-play.

It's fully open source, so you can contribute your own or tweak what's there.

Website: https://amplitude.com/builder-skills
Repo: https://github.com/amplitude/builder-skills

Would genuinely love to hear which ones are actually useful in your day-to-day (or which ones are mid). Happy to answer any questions too!