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

How to have a main agent delegate bug work to parallel chats with Lody

Use one coordinating conversation to split a bug into investigation, fix, and test conversations.

Who it is forAn engineer handling a bug that needs analysis, a code fix, and tests that can run in parallel.

The problemRunning several agent tasks by hand means tracking each one separately and collecting results manually.

The outcomeThe coordinating conversation creates child conversations, reads their status and history, sends follow-up instructions, and brings results back.

What you need first

  • A terminal where npx runs, on the machine you want to connect
  • A Lody account, since the daemon start command opens a sign-in link
  • At least one coding agent already set up on that machine, such as Claude Code, Codex, or another ACP-compatible Agent
  • A workspace name you can use with the CLI

Steps

  1. Open a conversation with a main Agent and describe the bug to analyze.
  2. Ask the main Agent to create separate conversations for investigation, implementation, and testing.
  3. Let the main Agent read each child conversation's status and history and send follow-up instructions where needed.
  4. Use an @ mention to reference a child conversation when you need to connect work across sessions.
  5. Run npx lody session list --workspace my-team to check the status of the child conversations from the CLI.

Prompt for your agent

In the LodyAI/Lody repo, act as the coordinating conversation for the bug <bug-description> in the workspace <workspace-name>. Create or reuse child conversations for investigation, implementation, and testing, then report each child conversation's status. Verify the statuses against the output of `npx lody session list --workspace <workspace-name>`.

Caveat. The README says child conversations stay independent while keeping a link to their creator, so results still need review before they are merged into your code.

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