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

How to read agent turns and memory in a browser debugger with Ufo Core

Open turns, steps, transcripts, and memory in a browser to see what an agent did.

Who it is forA developer or team lead who needs to check why an agent took an action before trusting its work.

The problemAn agent's run is hard to audit from the chat alone, especially when several turns or steps are involved.

The outcomeA browser view of a workspace's turns, steps, transcripts, and memory for review.

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 debugger
  2. Run make serve after the debugger build finishes
  3. Run uv run ufoctl debugger in a second terminal

Prompt for your agent

In the ufo-core repo, run `make debugger` before `make serve`, then run `uv run ufoctl debugger`. Expected output: a browser view of turns, steps, transcripts, and memory. Verify that at least one turn from the workspace appears before you report success.

Caveat. The debugger needs pnpm, and the README says make debugger must run before make serve.

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