# How Teams Use Agen Real workflows. Real results. From shipping features across repos to letting your PM push code changes — here's what autonomous agents actually look like in practice. ## Ship Features That Span Your Entire Stack ### The scenario You need to add Stripe billing. That means a new API endpoint in the backend, a settings UI in the frontend, and webhook configuration in your infra repo. With any other tool, that's three separate sessions you coordinate manually. ### Time ~20 minutes ### Cost Under $5 ### The real win You review one coordinated workflow instead of manually stitching together backend, frontend, and infra changes yourself. ### Features used [Multi-Repo Sessions](/content/features/multi-repo/index.html) [Cross-Repository Live Previews](/content/features/cross-repo-live-previews/index.html) [Self-Fixing Pipelines](/content/features/self-fixing-pipelines/index.html) ### With Agen 1. “Add Stripe billing to the settings page” 2. Agent clones all three repos 3. Backend: /api/billing endpoint, Stripe SDK, webhook handler 4. Frontend: settings page, plan selector, payment form 5. Infra: Stripe API keys, webhook URL in deployment config 6. Three linked PRs, one Cross-Repository Live Preview of the full billing flow 7. You test the checkout end-to-end in your browser, then merge all three ## Fix Bugs Without Context-Switching ### The scenario A user reports a 500 error on the /api/users endpoint. Normally you'd stop what you're working on, switch context, reproduce the bug, trace the issue, write the fix, test it, push it through CI, and open a PR. That's 30-60 minutes of your focused time gone. ### Time ~15 minutes ### Cost Under $3 ### The real win You never left what you were working on. The bug is fixed, tested, and ready to merge by the time you check your PR queue. ### Features used [Self-Fixing Pipelines](/content/features/self-fixing-pipelines/index.html) [Cross-Repository Live Previews](/content/features/cross-repo-live-previews/index.html) ### With Agen 1. “Fix the 500 error on the /api/users endpoint” 2. Agent clones the repo, reads the code, traces the error 3. Identifies the issue — missing null check on a database query 4. Writes the fix, adds a test case for the edge case 5. Pipeline runs, passes. Preview shows the endpoint working. 6. PR ready. You review a clean diff and merge. ## Maintenance That Runs Itself ### The scenario Your dependencies are 6 months out of date. Test coverage has been slipping. Nobody's checked for security vulnerabilities since the last audit. Everyone knows these things need attention. Nobody has time. ### The real win Your codebase stays healthy without anyone thinking about it. Maintenance happens on autopilot instead of in crisis mode. ### Features used [Scheduled Agents](/content/features/scheduled-agents/index.html) [Budget Controls](/content/pricing/index.html) [Alerts](/content/features/alerts/index.html) [Self-Fixing Pipelines](/content/features/self-fixing-pipelines/index.html) ### With Agen - **Daily at 6 AM:** Update patch/minor dependencies, run tests, open PR if green — Budget: $3/run - **Weekly on Monday:** Scan for CVEs, patch critical vulnerabilities, open PR — Budget: $10/run - **Monthly:** Run full code quality sweep (dead code, lint, imports), open PR — Budget: $15/run ### What you see PRs appear in your queue on a predictable cadence. Most are small, clean, and pass CI. You review and merge over coffee. If something needs attention, you get an Alert. ## Your PM Can Ship Code Now ### The scenario Your product manager wants to change the copy on the pricing page. Your designer wants to update the color of a button. Your founder wants to add a new FAQ question. All of these are 5-minute changes — but they're blocked behind the engineering queue because nobody else can touch the code. ### Time 5 minutes ### Cost Under $1 ### The real win Non-technical team members unblock themselves. Engineers review and merge instead of doing the work. The engineering queue shrinks. Everyone ships faster. ### Features used [Cross-Repository Live Previews](/content/features/cross-repo-live-previews/index.html) [Self-Fixing Pipelines](/content/features/self-fixing-pipelines/index.html) ### With Agen 1. PM opens Agen in their browser 2. “Change the pricing page headline to "Simple, Transparent Pricing" and update the Starter plan description to "For solo developers and small projects"” 3. Agent makes the changes, runs the pipeline, preview shows the updated pricing page 4. PM checks the preview — looks right 5. Engineer gets a PR notification, glances at the diff, merges ## Clear Your Backlog in a Day ### The scenario It's Monday. You have 15 tickets in the sprint. Each one is a well-defined task — add a feature, fix a bug, update a component, write a test. Your team of 3 engineers will spend the week on them. ### The real win Your team's job shifts from implementing to reviewing. The bottleneck moves from 'who's writing the code' to 'who's approving the PR' — and that's a much better bottleneck to have. ### Features used [Unlimited Parallel Agents](/content/pricing/index.html) [Self-Fixing Pipelines](/content/features/self-fixing-pipelines/index.html) [Cross-Repository Live Previews](/content/features/cross-repo-live-previews/index.html) ### With Agen 1. Assign all 15 tasks to agents — they start in parallel 2. Agents work simultaneously, each in its own sandbox 3. Within a few hours, 15 PRs land in your queue — each with passing CI and a live preview 4. Your team spends the day reviewing and merging instead of implementing 5. By Tuesday, the sprint is done ## What Would You Ship With Unlimited Agents? Free to start. No credit card. No setup.