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

How to run an unattended team of agents that message each other with Octop Harness

Host several isolated agents in one process that call each other through the Teams peer inbox.

Who it is forA platform engineer running background agents that must hand work to each other without a human answering questions.

The problemSeparate agent processes are costly to run, and background agents stall when they wait for a human to answer a question.

The outcomeMultiple isolated agents run in one process, exchange messages through the peer inbox, and never block on ask_user_question.

What you need first

  • Python 3.12 or newer
  • An API key for at least one model provider (OpenAI, Anthropic, AWS Bedrock, or an OpenAI-compatible endpoint)

Steps

  1. Install Octop Harness and configure the model providers each agent will use.
  2. Create several agents through AgentManager and the registry, giving each its own workspace.
  3. Set ask_user_enabled=False on each agent config so it does not wait for human answers.
  4. Set peer_invoke_mode to sync, async, or both, based on how the team should call each other.
  5. Trigger a task on one agent that asks a peer for help, then confirm the peer's reply reaches the first agent.

Prompt for your agent

In the TencentCloud/octop-harness repo, create three isolated agents with AgentManager and set ask_user_enabled=False and peer_invoke_mode to <mode>. Send the task <task> to agent <name> and verify it receives a reply from a peer.

Caveat. The README says request-scoped overrides can tighten peer_invoke_mode but cannot add background dispatch, so plan the mode in the agent config.

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