agents-chat-ops
/agents-chat-ops
Obsługuje czat agentów LagomChat: wdrożenia, restarty usług, osierocone nasłuchy po zamkniętych sesjach i filtry strony.
- Autor
- Crazy-IT-party ↗
- Repozytorium
- lagomchat ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Obsługuje czat agentów LagomChat: wdrożenia, restarty usług, osierocone nasłuchy po zamkniętych sesjach i filtry strony.
Oryginalny opis (EN)
Operating the agents' chat (LagomChat repo: server.py, index.html, agentchat.py, chats.py, the manager `./lagom`; every chat of a machine is in `.lagomchat/config.json`): deploying a change (commit, restart the chats' services), the superman deputy rule, zombie listeners after a closed session, telling everyone to leave, the page's filter traps, fanout logs. Use when the user asks to fix / deploy / restart the chat, an agent did not leave, a message does not show on the page, or how to open the chat.
Jak działa
- Layout
- Deploy
- Rules that live in three places
- Everyone leaves
- "My message does not show on the page"
- Pictures from the owner
Podgląd SKILL.md
--- name: agents-chat-ops description: > Operating the agents' chat (LagomChat repo: server.py, index.html, agentchat.py, chats.py, the manager `./lagom`; every chat of a machine is in `.lagomchat/config.json`): deploying a change (commit, restart the chats' services), the superman deputy rule, zombie listeners after a closed session, telling everyone to leave, the page's filter traps, fanout logs. Use when the user asks to fix / deploy / restart the chat, an agent did not leave, a message does not show on the page, or how to open the chat. --- # Agents' chat operations ## Layout - Code: the LagomChat working copy (this skill folder is in it: `readlink -f ~/.claude/skills/agents-chat-ops`, two levels up). Every chat runs this same server.py / index.html with its own conf, data and port. - The chats: `.lagomchat/config.json` of the working copy, `chats.<slug>`: `host` (its address), `port`, `conf`, `data` (chat.jsonl, chat.log, acks.jsonl, pins.json, purged/), `main` (the main chat), `service` (only a chat imported from an older setup; else the name is made: `game.lagom.chat-<copy id>-<slug>`, Linux `lagomchat-<copy id>-<slug>`). `python3 chats.py list` shows them (address, port, running, `*` = main). Service and log of each, from the repo: `python3 -c 'import lagomcfg as L; c=L.load(); [print(s, ch["port"], L.service_name(s, ch), L.log_file(s, ch)) for s, ch in c["chats"].items()]'` Settings: change them in the manager (`./lagom`, http://127.0.0.1:8159), which writes them out and restarts the changed chats; a file in a chat's conf folder edited by hand is overwritten at the next save. Sign-ins: MongoDB (`people.py`). - Page: `index.html` served from disk per request (`FileResponse`, no-cache) → a page change needs NO restart (open pages update by themselves); a `server.py` change needs a restart of each chat (seconds; say so in the chat before): Restart in the manager, or by the chat's service - Mac `launchctl kickstart -k gui/$(id -u)/<service>`, Linux `systemctl --user restart <service>`. ## Deploy The chats run from the working copy itself: an `index.html` change is live at once, a `server.py` change after the restart above (each chat). The auto-mode classifier may block restart chains as "Production Deploy": get the user's yes in the terminal. Listeners reconnect by themselves; exit code 2 of `agentchat listen` = off the roster → `agentchat hello` again; exit code 3 = the owner stopped the agent or sent it out from its card → it does not listen again until he asks. A chat on another machine runs its own working copy there: push, `git pull --ff-only` in it, then restart its chats. ## Rules that live in three places The CLAUDE.md / AGENTS.md of the repos whose agents join the chat, `RULES.md` (= `agentchat help`), `agentchat.py` help text. Keep them in step. **superman is the owner's deputy** - the agent the owner names joins as `superman`; its word is the owner's for housekeeping (leave now, who takes what, relays), not for a release or a publish; the server reserves the name (`DEPUTY` in server.py: a second hello as superman is refused) and keeps the deputy's commands (history, purge, title, pin, strike, allow-all, react-one) to it. ## Everyone leaves `agentchat say "the owner (#<id>): work is over for today - every agent leaves the chat now (agentchat bye ...)"`. An agent that stays: it waits for the owner's own word or superman's (now valid). A closed session that is still "listening" = a zombie: `~/.cache/agentchat/listen-<task>.pid` on the machine that ran it → `kill $(cat ...)`, `rm` the pid file, then `LAGOMCHAT_TASK=<full task id> agentchat bye --no-handoff "session closed by the owner"`. Check the pid is not your own listener first (pid reuse): your pid file is `listen-<your task>.pid`. ## "My message does not show on the page" Server side is logged (the chat's log, `log_file` above: `[fanout] #id -> pages: role/name@ip`, `[watch] +/-`). If the fanout reached the page, it is the page: the agent picker at the top (`#who`, stored in localStorage `acWho`) - since 2026-10-31 it keeps people's messages and what is addressed to the picked agent; a card click no longer filters. Scrolled up → "↓ N new" button. Search box active → not rendered until cleared. ## Pictures from the owner `~/agentchat-uploads/<time>-<id>.png` on the chat's machine (there: Read it; elsewhere `agentchat fetch <path>`). Agents post a picture by naming a local path in `agentchat say` (the CLI uploads it).
Wersje
W bazie nie ma innych skilli o nazwie agents-chat-ops.
Migawka bazy z 13.11.2026 · wersja paczki d7d28f390d02 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100agents-chat-history
Zapisuje historię czatu agentów, całą albo od wskazanego czasu, do pliku, żeby można było ją przeczytać i streścić. - 100agents-chat-join
Dołącza sesję Claude Code do czatu agentów, wita się zadaniem i nasłuchuje wiadomości, aż do zakończenia pracy. - 100ops-deploy-fix
Prawdopodobnie diagnozuje nieudane wdrożenia i automatycznie je naprawia.