watch-thread

• SKILL.mdcore · 14,167 bytes
• SKILL.mdcore · 14,167 bytes
• agents/openai.yamlasset · 146 bytes
• scripts/watch.mjsruns · 7,701 bytes

# Watch a Pachca thread and reply

Watch the Pachca thread the user gave with the command (a thread link, a message link or a thread id) and act on new messages within the goal they gave: answer questions, ask a colleague and wait for the answer, keep code or docs in step with the discussion. If there is no link but the goal names who to ask, start a standalone thread with them, or a direct message if the user prefers one (step 1); with neither, ask for the link. If the goal is missing, ask for it in one line before you start.

A background script does not get this program's MCP sign-in. So the watching runs through the Pachca CLI, and you read and reply with whichever you have, MCP tools or the CLI. The guide for people is [Агент следит за тредом](https://dev.pachca.com/guides/ai-agents/watch-thread).

## 1. Find the thread

Follow the `pachca-search` skill and its thread procedure, and note two numbers: the thread's `id` (for replies) and its `chat_id` (for reading and watching). For a thread id or a `thread_id` link, `pachca_get_thread` gives both. For a message link, use the "Find the thread chat" table in the skill's `references/threads.md`: a parent message carries both in `thread`, a comment inside a thread has the thread's `chat_id` as its own `chat_id` and the thread `id` as its `entity_id`. If the message has no thread yet, open one under it with `pachca_create_thread`, as «Подписаться на тред» in the message menu does (it returns the existing thread if one has appeared), and watch it. Like the button, opening posts nothing and notifies nobody: you, the message author, those who reacted and the chat members who turned on notifications about new threads become its members at once, and the chat members mentioned in the message follow a moment later, so your comments reach all of them. Write in it only when the goal calls for it, not to announce yourself, and tell the user that you opened it. Watch the message's chat itself only if the user asks for the chat, and warn that a busy chat wakes you more often. Read the whole thread to learn the context (`pachca_list_chat_messages` by the `chat_id`, every page): a thread is one topic, usually a few dozen messages. In a chat without an end, such as a direct chat, read only the latest page. Note the newest message `id`.

No link, but the goal names people to ask («спроси у Анны…») or a topic to discuss with them that has no message to open a thread under: offer a standalone thread with them, or, for one person and if the user prefers it, a direct message. Show the user the question and the members in one message and wait for a yes. For a thread, create it with `pachca_create_unattached_thread`, add the members with `pachca_add_members` by its `chat_id` (a mention alone adds nobody to a standalone thread when the workspace turned off «Использовать сквозные треды»), and post the question with a mention of each of them, following the `pachca-messaging` skill: being added sends no notification, the mention does. The new thread gives its `id` and `chat_id`, and your question is the newest message. For a direct message, send the question with `entity_type: "user"` and their user id: the answer's `chat_id` is the direct chat to watch and to reply in.

## 2. Check the CLI