---
site: steel.dev
collection: blog
canonical_url: https://steel.dev/blog/launch-week-v2-recap
markdown_url: https://steel.dev/blog/launch-week-v2-recap.md
content_signal: ai-input=yes, ai-train=yes, search=yes
related:
  - https://steel.dev/blog/launch-week-v2.md
  - https://steel.dev/blog/more-browsers.md
  - https://steel.dev/blog/webrtc.md
title: "Steel Launch Week v2: Everything We Shipped"
description: Five features that make AI agents work in production.
date: 2025-10-21
authors:
  - Hussien Hussien
category: Product
launch_week: v2
minutes: 2
tldr: "Steel Launch Week v2 shipped five features: Profiles for persistent browser identities, Mobile Mode, Agent Logs on a session timeline, headful sessions by default with WebRTC streaming and MP4 recordings, and doubled concurrency limits on all Steel Cloud plans, for example Pro/Startups from 50 to 100 sessions."
topics:
  - Browser automation
  - Persistent browser profiles
  - Mobile browser emulation
  - Agent debugging
  - Session recording
  - Concurrency limits
entities:
  - Steel
  - Steel Cloud
  - Profiles
  - Mobile Mode
  - Agent Logs
  - Headful Sessions
  - WebRTC
  - RRWeb
answers_questions:
  - What did Steel ship in Launch Week v2?
  - What does a Steel Profile store?
  - What are the new Steel Cloud concurrency limits per plan?
  - Why did Steel move live view and replay from Chrome screencasting to WebRTC?
---

# Steel Launch Week v2: Everything We Shipped

Launch Week v2 is done. Five days, five features.

We released production-ready updates that enable AI agents to work more reliably and effectively at scale.

Everything we shipped:

- [**Day 1:** Profiles](https://steel.dev/blog/profiles)
- [**Day 2:** Mobile Mode](https://steel.dev/blog/mobile-mode)
- [**Day 3:** Agent Logs](https://steel.dev/blog/agent-logs)
- [**Day 4:** Headful Sessions](https://steel.dev/blog/webrtc)
- [**Day 5:** Increased Concurrency Limits](https://steel.dev/blog/more-browsers)

## Day 1: Profiles

On Monday, we launched **Profiles** - persistent browser identities for your agents.

[Video on YouTube](https://www.youtube.com/watch?v=D2vG6K4skHg)

Before Profiles, every Steel session started fresh. Your agent would log in, complete a task, and when the session ended, everything was forgotten. Cookies cleared. Auth tokens gone.

Now your agents maintain persistent browser identities across sessions. A Profile stores cookies, extensions, credentials, localStorage, auth tokens, and fingerprints.

Your agent logs in once. Every subsequent session picks up with valid auth already in place.

[**Read more →**](https://steel.dev/blog/profiles)

## Day 2: Mobile Mode

On Tuesday, we added **Agent Logs** to the Steel dashboard.

[Video on YouTube](https://www.youtube.com/watch?v=mxRdCo3fjaA)

Pass `deviceConfig: { device: "mobile" }` when creating a session and the browser appears as a mobile device - user agent, viewport, touch capabilities, and browser characteristics all aligned.

Mobile sites present simpler DOMs, faster load times, and linear flows instead of nested menus. For AI agents, this simplification directly improves task completion rates and reduces token costs.

[**Read more →**](https://steel.dev/blog/mobile-mode)

## Day 3: Agent Logs

On Wednesday, we added **Agent Logs** to the Steel dashboard.

[Video on YouTube](https://www.youtube.com/watch?v=Vhx2u0Tynj0)

View every action your agent takes in a session (clicks, navigation, typing, scrolling) on a timeline next to the session viewer.

When your agent fails at a task, you can trace exactly where things went wrong. Click any event and the session viewer jumps to that point. You see what the agent saw, what it did, and what happened next.

No more watching entire session replays trying to spot the moment things broke.

[**Read more →**](https://steel.dev/blog/agent-logs)

## Day 4: Headful Sessions

On Thursday, we launched **Headful Sessions** as the default for all Steel sessions.

[Video on YouTube](https://www.youtube.com/watch?v=2ECtoukYN0M)

We rebuilt the entire live view and replay experience from the ground up. We moved from Chrome's screencasting to WebRTC-based streaming at 25fps and replaced RRWeb with MP4 recordings.

Now all sessions run headful with OS-level streaming that captures everything on screen: native OS alerts, dropdowns, PDF viewers, and dialogs. Recordings show exactly what happened with 1:1 accuracy.

[**Read more →**](https://steel.dev/blog/webrtc)

## Day 5: Increased Concurrency Limits

On Friday, we doubled concurrency limits across all Steel Cloud plans.

New limits:

- **Hobby:** 2 → 5 concurrent sessions
- **Starter:** 5 → 10 concurrent sessions
- **Developer:** 10 → 20 concurrent sessions
- **Pro/Startups:** 50 → 100 concurrent sessions

Run more agents in parallel without hitting rate limits or implementing complex queuing systems.

[**Read more →**](https://steel.dev/blog/more-browsers)

## That's a Wrap

Each of these features tackles a real problem we've seen teams struggle with: session state, debugging failures, performance bottlenecks, and scale constraints.

If you're building with any of these new features, we'd love to hear about it. Join us in [Discord](https://discord.gg/steel-dev) or tag us on X (Twitter) [@steeldotdev](https://twitter.com/steeldotdev).

Thanks for following along. Launch Week v3 coming soon.