DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to split independent jobs across parallel workers with Chat on Steroids

Send separate jobs to CoS workers at once and bring their results back into one ChatGPT conversation.

Who it is forA developer or team lead with several independent tasks, such as reviewing modules or updating docs, who wants them handled in parallel.

The problemWorking through several independent jobs one after another in a single chat is slow and mixes context between them.

The outcomeIndependent jobs run across workers, each keeping its own context, and their results return to the main chat for review.

What you need first

  • Windows 10/11, macOS 13 Ventura or newer, or a current desktop Linux with a Secret Service keyring
  • Chrome 125+, current Edge or Brave for the browser extension
  • A ChatGPT account or workspace that can create custom MCP apps
  • A tunnel and a restricted API key created at OpenAI for Core setup

Steps

  1. Complete the Get started steps in Settings → Setup, including connecting Core.
  2. Confirm that Workers are enabled; fresh installs enable two workers.
  3. List the independent jobs in one message and ask ChatGPT to split them across workers.
  4. Review each worker's returned result in the chat before accepting it.
  5. Send a follow-up task to one worker that picks up where its earlier context left off.

Prompt for your agent

Using the repo totec448-spec/chat-on-steroids, split these independent jobs across workers: <job-list>. Expected output: one result per job, each attributed to the worker that ran it. Verify that every job has a result and that no worker reports work on a job it was not given.

Caveat. Workers organize work but do not grant extra quota or model access, and the browser extension is not a public ChatGPT automation API.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page