Contextual Page Copilot
Let the assistant see the record and screen the user is on before it answers.
What it adds
A context layer that assembles a permission-filtered, compact description of the current route, record, and available actions and hands it to the assistant.
What your agent is told to do
5
What your agent is told to do
5-
1
Build the context by re-reading the record through the app's normal authorization path, not from what the client sent. The copilot must never see a field the signed-in user could not open directly.
-
2
Send a compact representation rather than the whole record: the fields shown on screen, the identifiers, the recent history entries, and counts in place of long collections. Do not attach entire attachment bodies or full audit logs.
-
3
Rebuild the context when the route, the record, the workspace, or the user's permissions change, and discard the previous one. A copilot answering about the record the user left is worse than one that admits it has nothing.
-
4
Split the copilot's replies into advice, which is free, and actions, which are presented as a proposal the user approves before anything changes.
-
5
The conversation surface, message storage, streaming, and cost ceilings belong to AI Chat Assistant. This feature owns only the assembly and freshness of the context passed into it.
Edge cases it handles
7
Edge cases it handles
7- Context must be filtered by the current user's permissions, not the record owner's. A shared record that hides certain fields from this viewer must hide them from the copilot too.
- Navigating between records without a full page load must invalidate the context. If it does not, the copilot silently answers about the previous record and sounds confident doing it.
- Large records will blow the token budget. Truncate deliberately, in a documented order, and say in the reply that the view was partial rather than quietly dropping half the data.
- Read-only advice and state-changing actions must be visually and structurally separate. An action must never fire as a side effect of the model mentioning it.
- When the context could not be fully assembled — a slow related query, a permission check that failed, a record still loading — tell the user the copilot is working from partial information instead of pretending otherwise.
- Permissions revoked mid-session must take effect on the next turn, not on the next page load.
- A record deleted while the conversation is open must produce a clear statement that it is gone, not answers drawn from the stale copy in context.
Definition of done
8
Definition of done
8- Context is assembled server-side from an authorized read and contains no field the viewer cannot see.
- Changing route, record, or workspace replaces the context before the next turn is sent.
- Records are summarised into a bounded representation rather than serialized in full.
- Actions are always proposals requiring explicit approval, and are distinct from advice in the interface.
- Incomplete or stale context is disclosed to the user in the reply.
- Conversation storage and streaming are delegated to AI Chat Assistant rather than reimplemented.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Streaming AI Responses
Streaming AI Responses
Show AI output as it is generated so long answers do not look frozen.
What it does
Incremental rendering of model output as it arrives, with a persisted authoritative copy once the stream closes.
How it works
- 1 Find the AI surfaces where the user waits on a long response and stream those. Short classification or extraction calls do not benefit and should stay as plain requests.
- 2 Buffer incoming bytes until they form complete characters and complete structural units before rendering, so partial output never appears as broken glyphs or half-open markup.
- 3 Treat the streamed text as provisional. When the stream closes, persist the provider's final message as the authoritative record and reconcile what is on screen against it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/streaming-ai-responses
AI Support Triage
AI Support Triage
Summarise each incoming support request and estimate how urgent it really is.
What it does
An automatic summary, urgency estimate, and likely problem area attached to every inbound support request, with the evidence behind each.
How it works
- 1 Run triage as a background job on arrival, using the app's existing queue and retry behaviour. The ticket must be visible and workable in its raw form the moment it lands, whether or not triage has finished.
- 2 Produce three separate outputs — a short summary, an urgency level, and a likely problem area — and store each with the quoted source statements from the ticket that support it, so a human can check the reasoning.
- 3 Define urgency in terms of business impact: who is blocked, how many, whether money or data is at risk. Compute it from what the ticket describes, not from how the writer sounds.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-support-triage
AI Suggested Support Answers
AI Suggested Support Answers
Give support agents a grounded first draft instead of a blank reply box.
What it does
A draft reply composed for the agent from the ticket, the customer's account state, and the approved internal knowledge, with sources attached and no ability to send itself.
How it works
- 1 Ground every draft in retrieved material: the ticket thread, the account's real state, and articles from the approved knowledge set. Attach the sources used to the draft so the agent can open and check each one.
- 2 Load the draft into the agent's normal reply editor, unsent and fully editable. There is no path in this feature that sends a message to a customer without an agent pressing send.
- 3 Define the commitments the app is not allowed to make in a draft — refunds, credits, delivery dates, guarantees of a fix — and strip or refuse any draft containing them, leaving that part for the agent to write.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/ai-suggested-support-answers
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.