Troubleshooting

Common problems

pond says command not found

Install it in Settings › General, and put ~/.local/bin on your PATH.

pond cannot reach Pond

Pond must be running. The command talks to it over a local socket.

pond list shows fewer agents than you expect

Ended agents are hidden. Use pond list --all.

A blob says Lost its terminal or Folder removed

The terminal helper lost the session, or the worktree folder is gone. The agent stays in the sidebar so you can see what happened.

The preview says "localhost:5173 is not answering."

The dev server stopped. Start it again and press Reload.

The browser tile will not open a site

It shows only the worktree's own addresses. Other addresses open in your default browser. An agent needs your click on the origin sheet for anything else.

Pond Computer cannot click or capture

Give Pond Computer.app Accessibility and Screen Recording in System Settings. The buttons in Settings › Computer use open the right panes. A new build may need the permissions again.

An agent that was driving does not stop

Press Esc or Ctrl-Esc, or click Stop in its terminal header.

A group task does not start by itself

The take mode is probably Ask. Click Take, or turn Auto on. Auto also waits for its limits: agents at a time, starts a day, and the Kadans usage brake.

A friend shows "Can't reach <name>"

Their side refused three times. They may have removed you.

No crash reports or usage counts are sent

That is expected in a build without report keys. Settings › Privacy says so.

Export diagnostics

Go to Settings › Help › Export diagnostics. Pond shows a sheet, "What is in this file", with Save to Downloads and Cancel. Nothing is sent. The file is named Pond-diagnostics-<UTC date-time>.zip and holds:

• README.txt and system.txt: versions, macOS, the Mac model class, memory, cores, and which features are on.
• logs/friends.log: the last 300 lines, scrubbed again.
• Up to 5 summaries of Pond's own crashes from the last 14 days, rewritten as text and scrubbed.

It never holds your tasks, terminals, code, feeds or other apps' reports. Read it before you share it.

Still stuck

Export diagnostics and send the zip to whoever supports your build. For a crash, the crash summary in the zip is the useful part.