Files
PaperClipAI/doc
Dotta 8f13ec4d51 fix(slack): link created tasks in default reply guidance (#15579)
## Thinking Path

> - Paperclip helps people manage AI agents and their tasks.
> - Slack agents use shared guidance to write their replies.
> - A reply can show a task ID without a link.
> - The person must then search for the task.
> - This change tells the agent to link each task it creates.
> - People can open the task directly from the reply.

## Linked Issues or Issue Description

**What existing behavior does this improve?**

Default communication guidance for Slack agents.

**Current behavior**

The guidance does not require a link when an agent creates a task.

**Proposed behavior**

Require a clickable link to each created task. Use its identifier or
title as the link text. Use a public URL supplied by Paperclip. Report
when no public URL is available.

**Reason and benefit**

People can open the task without a separate search.

Related work: https://github.com/paperclipai/paperclip/pull/13760
introduced the guidance.
https://github.com/paperclipai/paperclip/pull/15576 adds account
connection instructions and does not cover task links.

## What Changed

- Add task link instructions to the shared Slack communication guidance.
- Document the default and the existing conversation snapshot behavior.
- Add regression coverage for the guidance in channels and DMs.

## Verification

- Passed: `pnpm exec vitest run
server/src/services/chat-communication-guidance.test.ts` (10 tests).
- Passed: `git diff --check`.
- Local full typecheck and build could not finish: the container killed
compiler processes (exit 137; cgroup reports OOM kills). The full test
run was stopped after this resource limit. CI results are pending.
- Added checks for task links, public URL sources, and missing URLs in
Slack channels and DMs.

## Risks

- Low risk. This changes prompt text only.
- Existing conversations keep their original guidance snapshot. New
conversations receive the new default after deployment.
- This is agent guidance. It does not force a link into provider output.

## Model Used

OpenAI Codex, GPT-6. The runtime did not expose an exact model revision
or context window size. Used reasoning, code inspection, file editing,
and command execution.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge
2026-10-09 20:23:18 -05:00
..
…
…
…
…