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

How to fill a QA seat with a remote OpenAI key with Auto Swarm Shadow Adapter

Run a shadow-worker on a separate machine that uses its own OpenAI key for qa_tester tasks.

Credentials. This setup puts an OpenAI API key and an account password on a remote machine, so limit who can access that machine and rotate the key if it is exposed.

Who it is forA QA lead who has an OpenAI API key on a remote tester machine and wants that machine to handle qa_tester tasks in an AutoSwarm company workflow.

The problemQA tasks in a company DAG need a worker on a separate machine, and the tester wants to use a hosted model without moving the work onto the main server.

The outcomeA remote shadow-worker picks up qa_tester tasks, calls the OpenAI provider with the local key, and submits results back to the adapter queue.

What you need first

  • A working AutoSwarm install (the README links to HKUDS/AutoSwarm)
  • Python
  • A SHADOW_JWT_SECRET of at least 32 characters
  • Access to a local model server (Ollama) or an API key for Anthropic or OpenAI, depending on the use case

Steps

  1. On the remote tester machine, run export LOCAL_OPENAI_API_KEY="<your-openai-key>" with your own key. (inferred, check the README)
  2. Run shadow-worker --server-url http://192.168.1.100:8800 --username <username> --password <password> --role qa_tester --provider openai --model gpt-4o with your account details. (inferred, check the README)
  3. Start an AutoSwarm session with opc chat --mode company "Build feature X" so a qa_tester task is assigned.
  4. Watch the worker output to confirm it claimed the task and submitted a deliverable.
  5. Review the submission in the React portal before the phase moves on.

Prompt for your agent

Use the repo AhmadHassan-BTed/AutoSwarm-Shadow-Adapter to start a shadow-worker for the qa_tester role on <remote machine> with the openai provider and model gpt-4o. Expected output: the worker's log showing each claimed task and each submitted deliverable. Verify that the key is read from the LOCAL_OPENAI_API_KEY variable and not printed to the log.

Caveat. The README gives the tester example for OpenAI gpt-4o only, so other models from that provider are not shown as tested.

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