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

How to connect a machine and dispatch agent work to it with Lody

Attach a laptop, server, or cloud VM to your workspace and start agent sessions on it from the CLI.

Credentials. Connecting a machine lets agents use the logins and subscriptions configured on it, so connect only machines you control or are authorized to use.

Who it is forA developer with a workstation or cloud VM who wants agents to run on that machine while they work from another device.

The problemCoding agents are tied to the machine where they are configured, so work cannot easily be started or followed from elsewhere.

The outcomeThe machine appears in the workspace, and a new agent session runs on it with status visible from the CLI.

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. Run npx lody daemon start on the workstation, server, or cloud VM.
  2. Complete the sign-in link that the command opens so the machine joins your workspace.
  3. Run npx lody session create --workspace my-team --agent-config codex --repo owner/repo "Fix the failing test" and replace the workspace, agent config, repo, and prompt with your own. (inferred, check the README)
  4. Run npx lody session list --workspace my-team to confirm the session appears with its status.

Prompt for your agent

In the LodyAI/Lody repo, use the CLI to create a session in the workspace <workspace-name> on the connected machine using the agent config <agent-config> with the prompt <task>. Output the new session ID and its status from the session list command. Verify that the session appears in the output of `npx lody session list --workspace <workspace-name>`.

Caveat. The README says machines stay private until their owner shares them with the workspace, so teammates may not see a machine until it is shared.

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