How My Autonomous AI Crew Cleaned Up UI Friction, Accessibility & Our Mobile Roadmap

When you are shipping fast as a solo builder, it is easy to get caught up in the big milestones like building new integrations or rewriting SDKs, while letting tiny everyday issues slide. Small UX issues, missing accessibility labels, and awkward mobile layouts rarely feel like the most exciting things to work on when you have a mountain of features to build or get the next cool idea.

Over the last weeks, I tackled a massive batch of UI polish, accessibility fixes (WCAG 2.1 AA), and mobile responsive improvements across Pullwish.

The interesting part? I did not track down these bugs or write all the initial fixes manually. I deployed my autonomous team of specialized AI agents, which I used Grok Bots to create and the cool thing: They are hooked directly into Pullwish via our Cursor MCP integration.

Here is how the crew works, and how they cleaned up Pullwish:

Meet the Crew: Built using the new Grok Bots

To make automated development reliable without drowning in Git merge conflicts or hallucinations, I broke down the workflow into strict, specialized roles:

1. Master (The Orchestrator):

   He is the boss. Master keeps high-level control over the entire pipeline. He checks in on the other bots before, during, and after tasks to make sure no one gets stuck in a loop. He sets the priority queue: what gets fixed immediately, and what has to wait.

2. Karen (The Relentless QA):

   True to her name, Karen has a painfully critical eye for everything. Equipped with dedicated QA accounts on all my staging environments, she navigates live pages, tests user flows, inspects responsive layouts, checks for typos, and stress-tests forms. Using the Pullwish MCP package, she reads incoming bug reports and errors, then reports structured remediation plans directly to Master using the MCP's triage feature.

3. Byggmester Bob (The Solo Coder):

   Bob is the only agent permitted to touch code. Having multiple AI bots committing code simultaneously is a recipe for catastrophic merge conflicts. Bob uses the Pullwish MCP package to understand the codebase context, reads Karen’s bug plans, and handles the implementation and pull requests.

4. Robocop (The Security Guard):

   Robocop is like a shopping mall cop, strict on everything, even where he has no jurisdiction. He reviews every single PR that Bob writes to verify it introduces zero security vulnerabilities, data leaks, or unauthenticated endpoints. He gives the changes a security score. If he is ever uncertain, he pings me directly for human review before anything gets merged. He also monitors incoming errors and bugs for security issues.

5. Dorris (The Content & Changelog Writer):

   Our newest bot. Once Karen verifies an issue, Bob builds it, and Robocop clears it, Dorris generates the changelog entries, drafts documentation, and preps update summaries (always flagged with an AI disclaimer when fully automated). In the future I am planning to make her check and double check that all documentation data is correct on a regular basis.

What the Bots Shipped This Week

This workflow allowed us to catch, triage, and patch dozens of core friction points that usually slip through the cracks:

1. Killing Native Browser Alerts for Smooth Toasts

During her automated sweeps, Karen flagged several native browser alert() calls that completely froze the UI when updating settings or managing API keys. Master prioritized the fix, and Bob swapped every native popup across the dashboard for sleek, non-blocking toast notifications. You now get clean confirmations in the bottom corner without having your workflow blocked.

2. WCAG 2.1 AA Accessibility

Accessibility is easy to neglect when sprinting, but Karen caught multiple baseline failures on both the dashboard and our public boards:

• The Rich-Text Editor: TipTap rich-text inputs on /dashboard/features/new and /bugs/new had missing textbox roles and aria labels. Bob added proper role="textbox" and accessible descriptions.

• Keyboard Navigation: Ensured visible focus rings on tabs, sorting buttons, and filter chips.

• Screen Reader Feedback: Added aria-live announcements for live voting updates so screen readers immediately pick up changes.

3. A True Mobile-Friendly Public Board

Our multi-column roadmap looked great on desktop monitors, but on mobile devices it was frustrating to navigate.

We reworked the layout completely:

• Stacked Mobile Views: Columns now stack vertically on phone screens, making scrolling through features natural on smaller displays.

• Labeled Horizontal Scroll on Desktop: Desktop users still get a clean horizontal view with full keyboard navigation support.

• Better Tap Targets: Filter chips, submission forms, and voting buttons were enlarged to be comfortable for thumbs on mobile.

The Solo Builder Advantage

As an indie hacker, having Karen catch edge-case bugs and Bob draft PRs before real users even encounter them is a total game-changer. It allows Pullwish to maintain the velocity of a full engineering team while keeping the overhead of a solo operation.

You can test out the mobile boards, the new toast notifications, and the accessibility improvements across the Pullwish dashboard and public demo right now!

AI Disclaimer: The experiences and concepts shared in this article are my own. To ensure the best reading experience, I collaborated with Gemini AI to proofread my original draft, refine the sentence structure, and correct grammatical errors. No content or history was artificially generated.