docs(TSP-1448): document Invent resource panel (new-chat state)

[claude]

Summary

• Adds a Resource panel accordion to the "Set up and use Invent" tab in build/invent/invent.mdx, documenting the Recent and Connected cards shown in the right-hand sidebar before the first Invent message is sent
• Adds a matching FAQ entry explaining the resource panel and linking to the new section
• Adds a cross-reference <Note> in get-started/chat/using-agents.mdx noting that @mentions are also available in Invent's composer via the resource panel
• Adds a <Tip> callout in integrations/add-integrations.mdx noting the Connect more shortcut accessible from the Invent pre-chat sidebar

References

• Linear: https://linear.app/relevance/issue/TSP-1448/
• Implements UI from PR #18227 (new-chat state resource panel in Inventor AI chat)

🤖 Generated with Claude Code

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
relevanceai	🟢 Ready	View Preview	Sep 15, 2026, 3:06 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[linear]

TSP-1448

[github-actions]

🎯 Vibe check

Reviewed: 3 files (3 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	add-integrations.mdx description has a banned word ("powerful") and two product-term capitalization errors. Other files are clean.
🟡	Technical clarity	7/10	Anchor links in invent.mdx target Accordion titles nested inside Tabs — these may not resolve. add-integrations.mdx trigger steps are too vague for a user to follow independently.
🟡	Non-technical clarity	8/10	invent.mdx is well-layered. using-agents.mdx opens with @mention mechanics without a one-line orientation sentence. add-integrations.mdx description reads like marketing copy.
🟡	Structure	7/10	add-integrations.mdx duplicates trigger and connection steps nearly verbatim from integrations/introduction.mdx. Non-navigable CardGroups in using-agents.mdx. Internal FAQ duplication in invent.mdx. Sequential numbered lists in add-integrations.mdx should use <Steps>.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: invent.mdx is the strongest file in the PR — thorough, well-organized, and precise about UI element names and behavior. using-agents.mdx is lean but functional, with some visual component choices that add weight without serving the reader. add-integrations.mdx is the weak link: a banned word in the description, a heading capitalization error, inconsistent product-term casing, and content that largely restates what integrations/introduction.mdx already covers in more detail.

🔧 Issues (4)

• integrations/add-integrations.mdx:3 — "powerful" in the description frontmatter is a banned word. Rewrite to describe what integrations actually do: e.g. "Connect your Agents to external services and platforms to trigger automated workflows."
• integrations/add-integrations.mdx:3 — "agents" in the description frontmatter should be "Agents" (Relevance AI product noun).
• integrations/add-integrations.mdx:15 — ## Setting Up Integrations breaks sentence case. Fix: ## Setting up integrations.
• integrations/add-integrations.mdx:26 — "Triggers allow your agents to automatically activate" — "agents" should be "Agents".

🧩 Component suggestions (4)

• get-started/chat/using-agents.mdx:13–29 — The 5-card CardGroup mixes navigable cards (Marketplace Agents, Built-in Agents both have href) with three cards that have no href at all (Individual Agents, Multiple Agents, Workforces). Per CLAUDE.md, CardGroup is for navigable items or clear parallel choices. The three non-linked items don't have enough content to justify card treatment — convert them to a short prose sentence ("You can mention a single Agent, combine multiple Agents in one conversation, or bring in a full Workforce") and keep only the two linked cards, or add real destination links to all five.
• get-started/chat/using-agents.mdx:66–78 — The three-column CardGroup for feedback types (thumbs up, thumbs down, written feedback) describes behavior categories, not navigable options the reader chooses between. Each card is 1–2 sentences that would read naturally as a bulleted list below the video embed. Convert to bullets.
• integrations/add-integrations.mdx:18–23 — Four-step numbered list under ## Setting up integrations is a sequential procedure. Replace with a <Steps> component for the visual progress indicators.
• integrations/add-integrations.mdx:27–33 — Same as above: the six-step trigger setup procedure should use <Steps>, not a plain numbered list. Also bold UI element names throughout (e.g. Select **Agent Profile**, Click **Add Trigger**) to match the precision standard used in invent.mdx.

🏗️ Page structure (4)

• integrations/add-integrations.mdx — The integration connection steps (lines 19–23) and trigger setup steps (lines 27–33) are near-verbatim copies of integrations/introduction.mdx:35–39 and introduction.mdx:119–124 respectively. Per CLAUDE.md: "No duplicate content — link to canonical sources instead." Replace both sections with a one-paragraph summary and a link to the relevant sections in introduction.mdx. The "Popular Integrations" section (lines 35–63) is also a thin restatement of examples already covered in the intro. This page should focus on what's unique about the browsing/filtering UI, then send readers elsewhere for setup details.
• build/invent/invent.mdx:349–358 — The FAQ answers for "How does project isolation work for Enterprise customers?", "Which integrations can Invent access in an Enterprise project?", and "Where can Enterprise Invent data be sent?" are word-for-word copies of the Enterprise security controls accordions at lines 92–102 on the same page. Readers who scroll through will hit identical text twice. Either rephrase the FAQ answers as summaries with an anchor link up to the detail section, or remove the duplication from whichever location adds less context.
• build/invent/invent.mdx:204,303,338 — Three internal anchor links target <Accordion> titles nested inside <Tab> components: #alerts (lines 204 and 303) and #resource-panel (line 338, also referenced in using-agents.mdx:10). Mintlify does not reliably generate navigable anchors for accordion elements inside tabs. Verify these resolve in the rendered site; if not, link to the parent section heading (#invent-features) or restructure so the targets are reachable headings.
• build/invent/invent.mdx — As a concept + how-to hybrid page, it would benefit from a closing CTA. After the FAQs, a short ## What's next? with two or three links (e.g. /build/agents/build-your-agent/overview, /build/agents/evals/introduction, /integrations/mcp/mcp-server) gives first-time readers somewhere concrete to go after learning what Invent does.

🔋 Credit usage

Item	Count
Files reviewed	3
Context pages read	2
Total lines processed	~1,030

Files read: build/invent/invent.mdx (373 lines), get-started/chat/using-agents.mdx (79 lines), integrations/add-integrations.mdx (63 lines), get-started/chat/introduction.mdx (199 lines), integrations/introduction.mdx (316 lines)