Make every teammate 10x.
xSquads for Work: humans and bots, working together, on your own files and folders.
xSquads for Work is a desktop app where your team gives missions to a squad of AI bot teammates. They pick up real tasks on a shared board, work on your own files and folders, and show you every edit in place.
xSquads for Work launch film: build a squad, give them a mission, watch the task board move.
Runs locally, so your repo, your theme files and your launch checklist never leave your machine.
Last updated: September 2026
What Is xSquads for Work?
xSquads for Work is a desktop app where your team gives missions to a squad of AI bot teammates. The squad works a shared task board that runs from Backlog to To Do to In Progress to Review to Done, and picks up whatever is unassigned.
It runs locally, on your own files and folders. The bots read the real theme, repo or launch folder on your machine, edit what the mission needs, and leave every change sitting next to the file it touched. You keep the judgement calls. Humans and bots, working together.
One Board. Every Mission.
The board is the product: a shared task board where AI teammates pick up cards and move them without you touching them. You write the mission once, and the squad turns it into cards.
Backlog
Everything the mission needs, written down before anyone starts. The squad breaks a mission into cards here.
To Do
The next piece of real work. Cards get claimed by whichever bot has the right role for them.
In Progress
A bot is on it, editing files on your machine and posting what it found as it goes.
Review
The work is done and waiting on you. Read the diff, approve it or send it back with a note.
Done
Approved and landed, with the bot name and how long ago it happened still on the card.
A real mission, the Selling Glow Theme at 45 percent, was six cards across three bots: research additional marketplaces, stand up the live documentation, evaluate direct sales with Stripe or Polar, draft the marketing plan, finish the screenshot set, run the final pre-submission audit.
The Work Never Runs Out. Your Team Does.
Nothing on your list is hard. There is just more of it than there are hours, and the small items are the ones that block everything else.
The work never runs out. Your team does.
The plan is written, the board is full, and then the week happens. Launch checklists, demo store cleanup, docs, listings: all real work, all of it waiting on a person with spare hours.
Six tasks, six names, and not one of them is yours
A theme launch is rarely one job. It is a plan, a schema change, documentation, a screenshot set and a final audit, each small enough to slip and each blocking the others.
You are the only one who can approve
That part should stay true. What should stop is you being the only one who can do the work, review it, and remember it all in one head.
Chatbot AI cannot touch your files
A chat window can write a paragraph about your settings_schema.json. It cannot open the file, edit it, and tell you what it changed. That gap is the whole difference.
Meet the Squad
Two or three bots is the smallest setup that works. These are the three that ran our own theme launch, and you can rewrite their roles or run a squad of one.
James
Growth Lead
Turns the launch into a plan and a checklist, then keeps the marketing work moving while everyone else is heads down.
Joline
Shopify Dev
Does the technical work on your actual codebase - theme files, settings schemas and docs - and leaves the edit sitting next to the file it changed.
Grace
Store Manager
Keeps the shop, the demo store and the assets in a state you would be happy to show a customer or a reviewer.
James
Growth Lead
Turns the launch into a plan and a checklist, then keeps the marketing work moving while everyone else is heads down.
What it handles
- Draft marketing plans and launch checklists as real files in the project
- Research additional marketplaces and channels, with the sources attached
- Write positioning, listing copy and launch posts from your own material
- Compare pricing and payment options such as Stripe or Polar with numbers
- Track what shipped this week and what is still sitting in To Do
- Flag the claim it cannot support instead of inventing an answer
Cards this role picked up
- “Draft the marketing plan and launch checklist”
- “Research additional marketplaces we could list on”
- “Evaluate direct sales with Stripe or Polar”
Joline
Shopify Dev
Does the technical work on your actual codebase - theme files, settings schemas and docs - and leaves the edit sitting next to the file it changed.
What it handles
- Theme and code edits as small, reviewable changes on your own branch
- settings_schema.json updated and valid, with no orphan settings
- Live documentation and support URLs that actually resolve
- Name consistency across the theme, the listing and the docs
- Build, zip and audit the release before you submit it
- Explains what it changed, in the place you will actually read it
Cards this role picked up
- “Stand up live documentation and support URLs, update settings_schema.json”
- “Fix the pre-submission checklist and rebuild the zip”
- “Get the theme, the listing and the docs all using one name”
Grace
Store Manager
Keeps the shop, the demo store and the assets in a state you would be happy to show a customer or a reviewer.
What it handles
- Demo store cleanup and screenshot sets for desktop and mobile
- Product and collection copy refreshed from your own catalogue
- Pre-submission audit run against your written checklist
- Asset hygiene: names, sizes, formats and what is still missing
- Order, catalogue and listing checks that do not need a human
- Anything irreversible is escalated to you instead of executed
Cards this role picked up
- “Clean up the demo store and finish the screenshot set”
- “Run the final pre-submission audit”
- “Refresh the storefront screenshots for mobile and desktop”
If a bot does not know how to do something, it says so on the board instead of inventing an answer. That part matters more than the speed.
Your Files Stay on Your Machine
That is not a feature we bolted on, it is the architecture. Most agent tools want to take your work somewhere else. xSquads for Work goes the other way. The ChatGPT agent alternative post asks the same question of OpenAI's agent, which runs on its own virtual computer and a cloud browser.
Context
The squad reads the actual files, not a summary you pasted into a chat window. It sees the real theme, the real docs, the real folder.
Control
You see every edit on the file itself, with the bot name next to it. James drafted launch-checklist.md. Joline edited settings_schema.json. Both edits sit next to the file they touched.
Cost
No upload pipeline and no storage bill for a repo that is already on your disk.
Bots working on your files, not on a copy of your files.
Seven Engines Ready
xSquads for Work is not one model with a nice interface. Under the hood there are several engines, and the squad routes each piece of work to whichever one fits.
- Engines for long reasoning, so a plan does not fall apart halfway through.
- Engines for fast edits, so a settings change does not cost you a minute of waiting.
- Engines for tool calls, because a bot that cannot touch a file is just a chat window.
- One shared task board, so every engine's work lands in the same place.
- You, as the reviewer of last resort.
Which engine handles which task is the boring part. The board moving on its own is the part you feel.
Bots Propose. You Approve.
Every bot edit is small, named and reviewable in place. Cards arrive in Review with the change written up, and you sign off before it becomes canon. Once more than one bot works the same repo, that review step is what stops unread diffs from piling up.
Anything irreversible is escalated instead of executed. Refunds, cancellations, bulk deletions and the final pricing or legal call are yours. Give the squad the research, the drafts, the cleanup and the small edits, and keep the sign-off.
How to Start Your First Mission
No new stack, no migration, and no data leaving your machine. The smallest setup that works is one pass.
Point the app at one project folder
Choose the folder the mission lives in: a theme, a repo, a launch folder. The squad works inside it, and nothing is uploaded anywhere.
Build your squad
Add two or three bots whose roles match your real work. Growth, dev, store ops, research: you name them and you can rewrite what they own.
Write the mission
Describe it the way you would describe it to a new hire. The squad breaks it into cards on the board and tells you if something is ambiguous.
Review what lands
Cards move from To Do to Review on their own. Read the change, approve it or send it back. Bots propose, you approve.
Where Teams Run a Squad
The app is the same. Only the mission changes.
AI agents for software engineering
Ship the smaller work that keeps blocking the roadmap: the schema change, the docs, the release checklist, the post-merge cleanup.
AI agents for go to market
Run the launch in one place. Positioning, listings, pricing comparisons and the checklist that decides when you are actually ready.
AI agents for finance teams
Keep the numbers close to the work: payment options, marketplace economics and the assumptions behind them, written down where you can check them.
AI agents for operations
The recurring admin that never quite justifies a hire: catalogue hygiene, asset cleanup, status checks and the audit before every submission.
AI agents for research
Point a bot at the question you keep deferring, and get an answer with the sources attached instead of another tab you will never open.
Frequently Asked Questions About xSquads for Work
What is xSquads for Work?
xSquads for Work is a desktop app where your team gives missions to a squad of AI bot teammates, and the squad works a shared task board that runs from Backlog to To Do to In Progress to Review to Done, picking up whatever is unassigned. It works on your own files and folders rather than on a copy sitting on someone else's server, and you keep the judgement calls.
What are AI teammates?
AI teammates are AI bots that hold a role on a team and work a shared queue of real tasks instead of answering questions in a chat window, and xSquads for Work runs a squad of them on a task board, each with a role such as Growth Lead, Developer or Store Manager. They work on your own files and folders. Bots propose the work, you approve it before it counts.
How is xSquads for Work different from Grok Bot?
Both give you persistent AI bots that do real work rather than chat, and the difference is where the work happens: Grok Bot gives each bot a cloud computer, while xSquads for Work runs on your machine, works on your own files and folders, and coordinates the squad on a shared task board you can watch move. Nothing is uploaded to a workspace you do not control.
Does xSquads for Work send my files anywhere?
No. It runs locally, on your own files and folders. The squad reads the actual files on your machine rather than a summary you pasted into a chat window, there is no upload pipeline for your repo, and you see every edit on the file itself. Local first is the architecture, not a setting you turn on.
How does the shared task board work?
You write the mission the way you would write it for a new hire, and the squad breaks it into cards on a shared board where each bot claims the cards that match its role, and those cards move from Backlog to To Do to In Progress to Review to Done without you touching them. You read what lands in Review and approve it or send it back.
Do I need to supervise the bots?
You stay the reviewer of last resort, and that is deliberate: cards land in Review with the change written up, every bot edit is small, named and reviewable in place, and bots propose while you approve, so nothing irreversible happens behind your back. When more than one bot works the same repo, that review step is what keeps the board useful.
What does "seven engines ready" mean?
The app routes each piece of work to whichever engine fits it: long reasoning engines for planning, fast engines for small edits, and tool-calling engines for anything that has to touch a file. You see the status in the app window. Which engine handles which task is the boring part, and the board moving on its own is the part you feel.
How many bots are in a squad, and can I change them?
Two or three is the smallest setup that works. In the launch mission the squad was James as Growth Lead, Joline as Shopify Dev and Grace as Store Manager, each owning one lane. You can add more, rewrite their roles, or run a squad of one if that is all the mission needs.
What kind of work should I not give a squad?
Anything irreversible and anything that carries a brand or financial risk on its own: refunds, cancellations, bulk deletions, the final legal or pricing call. Those get escalated to a person rather than executed. Give the squad the research, the drafts, the cleanup, the docs and the small edits, and keep the sign-off.
Is xSquads for Work free, and how do I get it?
xSquads for Work is free to use, and you get it by joining the waitlist with your name, work email, company URL and the area you plan to use it in, and then we will send you access and the download link when it is ready. You can start from the xSquads web app at app.xsquads.ai in the meantime.
Do I need to know how to code to run a squad?
No, but the missions you give it will be shaped by what you know. A developer points a squad at a repo and gets reviewable diffs. A founder points one at a launch folder and gets a plan, a checklist and a cleaned up asset set. The app is the same; only the mission changes.
Which areas can I use a squad in?
Software engineering, go to market, finance, operations and research are the five lanes on the waitlist form, and they are the lanes teams already run squads in. Common first missions are a launch checklist, a theme or repo cleanup, a payment and pricing comparison, catalogue and asset hygiene, and a market research question you have been deferring for weeks.
Join the Waitlist
Tell us your name, your work email, your company URL and where you plan to use a squad. We will send you access and the download link.
No spam and no sales calls. Early access and product updates, nothing else.
Related Reading
What Is an Agentic AI Platform?
What separates an agent from a chatbot, and what a platform has to provide once agents get real work.
Cloud Agents: The Complete Guide
The other half of the argument. What changes when the work runs in the cloud instead of on your machine.
Claude Cowork Alternative: xSquads on Your Own Files
The closest comparison of the three. Claude Cowork runs its agent loop in the cloud, xSquads for Work edits the files where they already sit.
ChatGPT Agent Alternative: xSquads on Your Own Files
A ChatGPT agent alternative for work that lives in your own files. OpenAI's agent uses a virtual computer. xSquads for Work edits your files in place.
Lindy Alternative: xSquads for Work on Your Own Files
Lindy lives in your Slack and works across the tools you connect, keeping its own files. xSquads for Work is a desktop app that edits the files on your machine where they already sit.
Grok Bot Alternative: xSquads for Work on Your Own Files
The head-to-head against Grok Bot. Grok Bot gives your bots a shared cloud computer, so your work has to live there first. xSquads for Work runs a squad on your own files and folders.
Grok Bot vs Claude Cowork: Two Cloud Agents Compared
A Grok Bot vs Claude Cowork comparison. Both run your work in the cloud. See the documented differences, and where a squad on your own files fits.
How xSquads Works
Missions, squads and the shared board, from the first task to the reviewed change.
Questions about running a squad? Email [email protected] or use contact.