You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Deleted agents still listed after deleting them in the app (WhatsApp Orchestrator) #7437
Pengguna menghapus dua agen "WhatsApp Orchestrator" lewat aplikasi setelah WhatsApp diputus, tetapi keduanya masih muncul di daftar agen dan foldernya masih ada. Seharusnya agen yang dihapus hilang dari daftar dan dari folder.
Steps to reproduce
Hubungkan WhatsApp lewat Marketplace; agen "WhatsApp Orchestrator" dibuat otomatis (dua agen muncul setelah sambung ulang).
Putuskan koneksi WhatsApp; daftar koneksi kosong.
Hapus kedua agen orkestrator secara manual di aplikasi.
Daftar agen dan folder agen masih memuat keduanya.
Recent errors in the chat
Gathering the relevant information…: {"error":"No enabled connection has that id. Call openbot.messaging_list_places for the ids."}
openbot.messaging_list_places: {"error":"No enabled connection has that id. Call openbot.messaging_list_places for the ids."}
Working through the next tool-assisted step…: {"error":"Invalid tool discovery arguments. Use the declared schema and an original qualified tool name."}
Sent from the OpenBot app. An agent wrote this text, and the user approved it before it was sent.
Another report of this problem from the OpenBot app.
Title
Deleting an agent leaves it in the agent list
Area
Agents and providers
Severity
Works, but incorrectly or slowly
What happened?
Same failure on another agent: the owner deleted the Watchdog agent, and it still appears in the agent list, with read_agent returning it and both its routines intact. It happened yesterday with the executive assistant too, so a restart has been needed both times.
Steps to reproduce
Delete the agent in the app.
Ask another agent to list agents, or read the deleted agent by id.
The agent is still returned with its routines, so the delete had no visible effect until the app is restarted.
Platform
Windows
Installation source
Other
OpenBot version
0.68.0
Operating system and hardware
Windows 10.0.22631 (x64)
Agent runs on
Desktop app
Seen in
Desktop app
Providers
OpenCode
Provider CLI version
2.2.7
Model
opencode-go/deepseek-v4.1-flash
Reasoning effort
high
Sent from the OpenBot app. An agent wrote this text, and the user approved it before it was sent.
Activity
openbotgit commentedon Nov 12, 2026
Another report of this problem from the OpenBot app.
Title
Deleting an agent leaves it in the agent list
Area
Agents and providers
Severity
Works, but incorrectly or slowly
What happened?
Same failure on another agent: the owner deleted the Watchdog agent, and it still appears in the agent list, with read_agent returning it and both its routines intact. It happened yesterday with the executive assistant too, so a restart has been needed both times.
Steps to reproduce
Platform
Windows
Installation source
Other
OpenBot version
0.68.0
Operating system and hardware
Windows 10.0.22631 (x64)
Agent runs on
Desktop app
Seen in
Desktop app
Providers
OpenCode
Provider CLI version
2.2.7
Model
opencode-go/deepseek-v4.1-flash
Reasoning effort
high
Sent from the OpenBot app. An agent wrote this text, and the user approved it before it was sent.