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

How to hand a task to an agent in a hosted sandbox with Ufo Core

Give an agent a task from the terminal that keeps running in a sandbox after the client exits.

Remote script. The install step pipes a remote script from ufo.ai into sh, so check the script or the source before you run it on a machine that holds other credentials.

Who it is forA developer who wants an agent to do a longer task, such as a repo change, without tying up a laptop.

The problemLocal agent runs stop when the terminal closes, and running them on a laptop exposes local files to the agent.

The outcomeAn agent working in the workspace sandbox, with the turn continuing after ufo exits and the result readable later with --resume.

What you need first

  • Python with uv installed (https://docs.astral.sh/uv/)
  • API keys for the three model providers, set in .env
  • For remote sandbox use: a hosted UFO workspace, or a self-hosted server with a configured sandbox carrier
  • For Postgres or the debugger: make and pnpm

Steps

  1. Run curl -fsSL https://ufo.ai/ufo | sh
  2. Run ufo and sign in
  3. Run ufo --remote followed by your task in quotes (inferred, check the README)
  4. Run ufo --remote --resume ID with the turn ID to read the rest of the output (inferred, check the README)

Prompt for your agent

Use the ufo client from the ufo-core repo to send the task <task description> with `ufo --remote`. Expected output: a turn ID and a sandbox result under /workspace. Verify the turn ID by running the resume command before you report the result.

Caveat. The hosted service needs a workspace created at ufo.ai, and the README does not say what the --wait flag is measured against beyond its seconds value.

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