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

How to run a shared team agent server on one machine with Ufo Core

Install UFO on SQLite and local files so a small team can chat with agents on its own hardware.

Credentials. The three model API keys and the CLI token in ~/.ufoctl/token grant access to your model accounts and workspace, so keep .env and the token private.

Who it is forA developer or IT admin at a small team who wants agents for the team without sending work through a hosted service.

The problemTeam members want agents that can read files and run commands, but the team wants the runtime and its data on its own machine.

The outcomeA running UFO server on localhost where the admin is the workspace owner and a terminal client can send work to an agent.

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 make install
  2. Run cp .env.template .env and set the three model API keys in .env
  3. Run make build
  4. Run make init [email protected] with your work email
  5. Run make serve and keep it running, then open a second terminal

Prompt for your agent

In the ufo-core repo, follow the Quick start to run `make install`, `make build`, `make init EMAIL=<work email>`, and `make serve`. Expected output: the server listens on http://localhost:8710 and `~/.ufoctl/token` exists. Verify that `curl http://localhost:8710` returns a response before you report success.

Caveat. The default local sandbox can read the whole host and the kernel does not enforce its egress, so use docker or e2b for untrusted input.

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