Director

Every project has one Director: a single shared conversation for the project. It reads the project's chats and tickets, answers questions about them with links to the source chats, and starts new work when someone asks.

Who can talk to it

Everyone with access to the project can open the Director and send it messages. Each message shows who sent it. To control access, open the project's Access tab. Roles are set in Settings, Workspace, Members.

With the Slack plugin, allowed people can also talk to the Director from Slack.

Open the Director

1. In the sidebar, click the row with the compass icon under your project. It is called "*Project name* Director".
2. Type in the message box, or click a starter: Brief me, Find a chat or Start work.

What it can do

The Director only sees its own project. It can:

• Answer questions about the project's chats and tickets, with links to the chats it used.
• Find tickets, for example unanswered tickets, stalled tickets or tickets assigned to you.
• Start chats in the project for work someone asks for. The result returns to the Director automatically. You can name a model, for example "Opus 5.5 medium". If you do not, the chat uses the project's default model.
• Send a message into an existing chat. The chat's reply returns to the Director when it finishes.
• Add a private note to a FreeScout or Help Scout ticket. The note says which Director added it and who asked. WordPress.org has no private notes.
• Tag people by name or email when someone must act. Repile members get an Inbox and Triage item. With Slack connected, people are also mentioned in Slack, even when they have no Repile account.
• Save facts to project memory, such as who handles which product.

The Director never replies to customers. To get a reply drafted, ask the Director to ask that ticket's chat for a draft. Merging, approvals and customer replies always wait for a person.

Digests and alerts

All three features are off by default. Turn them on in the project's settings, on the Director tab. You can also click the settings button in the Director header.

Daily digest

Once a day, the Director posts a short summary of unanswered and stalled tickets and open pull requests. Every member gets an Inbox item and a notification.

1. Turn on Send a Daily digest.
2. Set the time in At and the timezone in in.
3. Optional: turn on Weekdays only (Monday to Friday).

Click Send a Daily digest now to test it.

Stall alerts

When nothing happens on a ticket for the set time after Repile's last note, the Director tags someone once per note.

1. Turn on Send Stall alerts.
2. Set Alert after in days. The default is 1 day. The same threshold marks tickets as Stalled in the sidebar.
3. In Whom to tag, pick one: Assignee, else the last person who replied, The last person who replied, The assignee or Nobody (all project members).

Unanswered alerts

When a customer has waited for a team reply for the set number of hours, the Director tags the assignee, else the last person who replied, once per customer message. Stalled tickets get a stall alert instead.

1. Turn on Send Unanswered alerts.
2. Set Alert after in hours. The default is 24 hours.

Digests and alerts post in the Director chat, add Inbox and Triage items and send push notifications. With Slack connected, they also post to the project's Slack channel. Code decides when alerts fire and whom to tag.

Director instructions

Director instructions tell the Director how to behave in its own chat and in Slack: tone, humor, emoji, whom to tag and how to report. Only the Director reads them. Ticket chats and other project chats follow the project's instructions.

1. Open the project's Director tab.
2. Write in Director instructions, for example "Keep reports short. Tag Steve for billing questions." You can use up to 1,800 characters.
3. Click Save instructions.

A change reaches the Director when its session next starts.

See what it did and stop it

The Director acts without approval cards. Every action is logged with who asked for it.

1. Click Activity in the Director header to see Director activity.
2. While the Director or a chat it started is working, click Stop.

Any project member can press Stop. It stops the chats the Director started and removes its unsent queued messages. Notes it already added stay.

From the CLI

repile projects director tell "My Plugin" "Summarize this week and link the source chats"
repile projects director digest "My Plugin" --enable --time 09:00 --timezone Asia/Jakarta --weekdays-only
repile projects director stall-alerts "My Plugin" --enable --after-days 2
repile projects director unanswered-alerts "My Plugin" --enable --after-hours 24
repile projects director stop "My Plugin"