Skip to content

Update overview#1119

Open
DianaHackmamba wants to merge 2 commits into
mainfrom
update-overview
Open

Update overview#1119
DianaHackmamba wants to merge 2 commits into
mainfrom
update-overview

Conversation

@DianaHackmamba

@DianaHackmamba DianaHackmamba commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Minor update, but the main issue is that we need to explain "agent brain." This is not an industry standard term.

Summary by CodeRabbit

  • Documentation

    • Reorganized agent documentation under a new "Connect" section with improved structure and navigation.
    • Added managed agent quickstart guide with step-by-step setup instructions.
  • Chores

    • Updated navigation menu and internal documentation links across the platform.
    • Implemented automatic redirects from legacy documentation paths to new structure.

@greptile-apps

greptile-apps Bot commented Jun 4, 2026

Copy link
Copy Markdown

PR author is not in the allowed authors list.

@netlify

netlify Bot commented Jun 4, 2026

Copy link
Copy Markdown

Deploy Preview for docs-novu ready!

Name Link
🔨 Latest commit 7d5d5d0
🔍 Latest deploy log https://app.netlify.com/projects/docs-novu/deploys/6a21c26bd2182b000828d668
😎 Deploy Preview https://deploy-preview-1119--docs-novu.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

This pull request restructures the documentation by migrating agent-related content from the /agents namespace to a new /connect namespace. The changes include: updating routing infrastructure (Next.js config, middleware, and navigation UI); registering the new /connect section in documentation metadata; introducing a new Connect landing page explaining Agent Communication Infrastructure; creating and updating managed agent documentation; updating all internal links throughout custom code agent guides; and updating cross-document references in mental model and platform integration pages. A backward-compatibility redirect layer maps old /agents/* paths to their /connect/* equivalents.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

  • novuhq/docs#1078: Updates /agents documentation routing in src/middleware.ts and related navigation configuration, establishing the baseline routing infrastructure that this PR depends on for the namespace migration.
🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check ❓ Inconclusive The title 'Update overview' is vague and generic, using non-descriptive language that fails to convey the actual scope of changes, which involve a major documentation restructuring from /agents to /connect routes and significant content reorganization. Revise the title to be more specific and descriptive, such as 'Reorganize agent documentation under /connect route' or 'Migrate agent docs from /agents to /connect', to clearly communicate the primary change.
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)
content/docs/connect/get-started/mental-model.mdx (1)

56-59: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Clarify “agent brain” as a non-standard term the first time it appears.

This section still uses “agent brain” without explicitly mapping it to a standard concept (for example: “your agent runtime/decision logic”). Adding one short definition here would satisfy the PR objective and reduce ambiguity.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/docs/connect/get-started/mental-model.mdx` around lines 56 - 59,
Update the first occurrence of the term "Agent brain" to include a short
parenthetical definition mapping it to a standard concept (e.g., "Agent brain
(your agent runtime/decision logic)") so readers understand it; keep the rest of
the paragraph intact but ensure the example call mention of ctx.reply() still
follows the clarified term and reads naturally (e.g., "your agent brain (your
agent runtime/decision logic) ... and calls ctx.reply()").
content/docs/connect/get-started/what-is-aci.mdx (1)

48-55: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Tighten and standardize the “Agent brain” definition.

The current text is hard to parse and mixes terminology/capitalization (“platfrom,” “lanchain,” “agent sdk”). Please rewrite this block to explicitly define “agent brain” in standard terms and separate custom-code vs managed-agent behavior clearly.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/docs/connect/get-started/what-is-aci.mdx` around lines 48 - 55,
Rewrite the "Agent brain" section to a concise, standardized definition and two
clear subsections: first define "Agent brain" as the component that determines
an agent's decision-making and actions; then a "Custom code agent" paragraph
explaining that you implement the brain with developer code or frameworks
(reference Agent brain, Custom code agent, agent SDK, LangChain) — describe that
your server receives a context object and can call an LLM, run business logic,
or route to humans; and a "Managed agent" paragraph (reference Managed agent,
Claude) explaining that a hosted platform provides the intelligence and built-in
tools (e.g., grep, web search) and integrations (e.g., Linear, Notion via MCP).
Fix capitalization and typos (platform, LangChain, Agent SDK) and keep tone
direct and parallel between the two cases.
🧹 Nitpick comments (1)
content/docs/connect/meta.json (1)

4-4: ⚡ Quick win

Use a descriptive section metadata description instead of "Connect".

A one-word description weakens search/snippet context for the section; use a concrete summary aligned with the new landing page positioning.

Suggested diff
-  "description": "Connect",
+  "description": "Build, deploy, and observe AI agents across chat platforms using Novu Connect and ACI.",
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/docs/connect/meta.json` at line 4, Replace the one-word "description"
value in meta.json with a concise, descriptive summary that explains what the
"Connect" section covers and aligns with the new landing-page positioning;
update the "description" field in content/docs/connect/meta.json to a 1–2
sentence blurb (roughly 50–120 characters) using target keywords from the
landing page, focusing on user benefit and scope so search/snippets show useful
context rather than a single word.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@content/docs/connect/custom-code-agent/setup-your-agent/edit-sent-messages.mdx`:
- Line 12: Replace the non-contracted phrase "That is not a [reply
type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message
you already sent." with a contracted form to match doc tone — e.g., change "That
is not" to "That's" so the sentence reads "That's not a [reply
type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message
you already sent." Update the exact text in the edit-sent-messages.mdx content
where that sentence appears.

In `@content/docs/connect/index.mdx`:
- Line 9: Fix the grammar in the opening paragraph by changing “enable you
interact with your agents” to “enable you to interact with your agents” in the
sentence that starts “Novu Connect uses the Agent Communication Infrastructure
(ACI)...”; update that sentence so it reads "...to enable you to interact with
your agents across different messaging platforms."
- Around line 22-25: Add a one-sentence definition of "agent brain" in Novu
terms immediately after the "## Connect your agent brain" heading and before the
sentence "Novu Connect accepts two kinds of agent brains." The sentence should
briefly define an agent brain as the service or model that provides the agent's
decision-making and context (e.g., "An agent brain is the service or model that
powers an agent's decision-making and contextual understanding for handling user
interactions."), then keep the existing managed vs custom explanation intact.

In `@content/docs/connect/managed-agent/quickstart.mdx`:
- Line 61: The page uses the acronym "MCP" before defining it; update the first
occurrence (the sentence that currently reads "Novu will generate the agent for
you, including its system prompt, tools, MCP servers, and skills based on your
description.") to "Model Context Protocol (MCP)" on first mention and leave
subsequent mentions as "MCP"; also update the other occurrences referenced (the
instances around the current text and the lines noted later) so they
consistently use the full term on first use and the acronym thereafter.

---

Outside diff comments:
In `@content/docs/connect/get-started/mental-model.mdx`:
- Around line 56-59: Update the first occurrence of the term "Agent brain" to
include a short parenthetical definition mapping it to a standard concept (e.g.,
"Agent brain (your agent runtime/decision logic)") so readers understand it;
keep the rest of the paragraph intact but ensure the example call mention of
ctx.reply() still follows the clarified term and reads naturally (e.g., "your
agent brain (your agent runtime/decision logic) ... and calls ctx.reply()").

In `@content/docs/connect/get-started/what-is-aci.mdx`:
- Around line 48-55: Rewrite the "Agent brain" section to a concise,
standardized definition and two clear subsections: first define "Agent brain" as
the component that determines an agent's decision-making and actions; then a
"Custom code agent" paragraph explaining that you implement the brain with
developer code or frameworks (reference Agent brain, Custom code agent, agent
SDK, LangChain) — describe that your server receives a context object and can
call an LLM, run business logic, or route to humans; and a "Managed agent"
paragraph (reference Managed agent, Claude) explaining that a hosted platform
provides the intelligence and built-in tools (e.g., grep, web search) and
integrations (e.g., Linear, Notion via MCP). Fix capitalization and typos
(platform, LangChain, Agent SDK) and keep tone direct and parallel between the
two cases.

---

Nitpick comments:
In `@content/docs/connect/meta.json`:
- Line 4: Replace the one-word "description" value in meta.json with a concise,
descriptive summary that explains what the "Connect" section covers and aligns
with the new landing-page positioning; update the "description" field in
content/docs/connect/meta.json to a 1–2 sentence blurb (roughly 50–120
characters) using target keywords from the landing page, focusing on user
benefit and scope so search/snippets show useful context rather than a single
word.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 29755c25-71ec-4abf-9ff1-04608d0e48af

📥 Commits

Reviewing files that changed from the base of the PR and between 112a194 and 7d5d5d0.

⛔ Files ignored due to path filters (2)
  • public/images/agents/managed-agent/agent-message-slack.png is excluded by !**/*.png
  • public/images/agents/managed-agent/novu-connect-demo.gif is excluded by !**/*.gif
📒 Files selected for processing (37)
  • content/docs/agents/managed-agent/quickstart.mdx
  • content/docs/connect/conversations.mdx
  • content/docs/connect/custom-code-agent/build-your-first-agent.mdx
  • content/docs/connect/custom-code-agent/concepts.mdx
  • content/docs/connect/custom-code-agent/going-to-production.mdx
  • content/docs/connect/custom-code-agent/meta.json
  • content/docs/connect/custom-code-agent/quickstart.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/connect-components.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/connect-components.model.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/create-an-agent.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/edit-sent-messages.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/handle-events.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/meta.json
  • content/docs/connect/custom-code-agent/setup-your-agent/overview.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/reply.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/scaffold-your-project.mdx
  • content/docs/connect/custom-code-agent/setup-your-agent/signals.mdx
  • content/docs/connect/get-started/agents-and-providers.mdx
  • content/docs/connect/get-started/mental-model.mdx
  • content/docs/connect/get-started/meta.json
  • content/docs/connect/get-started/what-is-aci.mdx
  • content/docs/connect/index.mdx
  • content/docs/connect/managed-agent/add-skills.mdx
  • content/docs/connect/managed-agent/concepts.mdx
  • content/docs/connect/managed-agent/configure-mcp-servers.mdx
  • content/docs/connect/managed-agent/meta.json
  • content/docs/connect/managed-agent/overview.mdx
  • content/docs/connect/managed-agent/quickstart.mdx
  • content/docs/connect/meta.json
  • content/docs/meta.json
  • content/docs/platform/integrations/chat/(providers)/ms-teams.mdx
  • content/docs/platform/integrations/chat/(providers)/slack.mdx
  • content/docs/platform/integrations/chat/(providers)/whats-app.mdx
  • content/docs/platform/integrations/chat/index.mdx
  • next.config.mjs
  • src/app/layout.config.tsx
  • src/middleware.ts
💤 Files with no reviewable changes (1)
  • content/docs/agents/managed-agent/quickstart.mdx

`ctx.reply()` returns a `ReplyHandle` so that you can edit the message you just sent on the provider. This is useful when you post "Processing..." and replace it with the final text.

That is not a [reply type](/agents/custom-code-agent/setup-your-agent/reply); it updates a message you already sent.
That is not a [reply type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message you already sent.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Use contraction for smoother doc tone on Line 12.

Line 12 can be tightened to match the doc style/lint expectations.

Suggested edit
-That is not a [reply type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message you already sent.
+That's not a [reply type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message you already sent.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
That is not a [reply type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message you already sent.
That's not a [reply type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message you already sent.
🧰 Tools
🪛 GitHub Check: vale

[notice] 12-12: [vale] content/docs/connect/custom-code-agent/setup-your-agent/edit-sent-messages.mdx#L12
[Google.Contractions] Use 'that's' instead of 'That is'.


[notice] 12-12: [vale] content/docs/connect/custom-code-agent/setup-your-agent/edit-sent-messages.mdx#L12
[write-good.E-Prime] Try to avoid using 'is'.


[notice] 12-12: [vale] content/docs/connect/custom-code-agent/setup-your-agent/edit-sent-messages.mdx#L12
[Google.Semicolons] Use semicolons judiciously.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@content/docs/connect/custom-code-agent/setup-your-agent/edit-sent-messages.mdx`
at line 12, Replace the non-contracted phrase "That is not a [reply
type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message
you already sent." with a contracted form to match doc tone — e.g., change "That
is not" to "That's" so the sentence reads "That's not a [reply
type](/connect/custom-code-agent/setup-your-agent/reply); it updates a message
you already sent." Update the exact text in the edit-sent-messages.mdx content
where that sentence appears.


import { Code2, Sparkles, BrainCircuit, Blocks, MessagesSquare, CircleHelp, Zap } from 'lucide-react';

Novu Connect uses the [Agent Communication Infrastructure (ACI)](/connect/get-started/what-is-aci), which is the infrastructure layer that handles how agents communicate, to enable you interact with your agents across different messaging platforms.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Fix grammar in the opening paragraph.

Use “enable you to interact” for correct phrasing.

Suggested diff
-Novu Connect uses the [Agent Communication Infrastructure (ACI)](/connect/get-started/what-is-aci), which is the infrastructure layer that handles how agents communicate, to enable you interact with your agents across different messaging platforms.
+Novu Connect uses the [Agent Communication Infrastructure (ACI)](/connect/get-started/what-is-aci), which is the infrastructure layer that handles how agents communicate, to enable you to interact with your agents across different messaging platforms.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Novu Connect uses the [Agent Communication Infrastructure (ACI)](/connect/get-started/what-is-aci), which is the infrastructure layer that handles how agents communicate, to enable you interact with your agents across different messaging platforms.
Novu Connect uses the [Agent Communication Infrastructure (ACI)](/connect/get-started/what-is-aci), which is the infrastructure layer that handles how agents communicate, to enable you to interact with your agents across different messaging platforms.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/docs/connect/index.mdx` at line 9, Fix the grammar in the opening
paragraph by changing “enable you interact with your agents” to “enable you to
interact with your agents” in the sentence that starts “Novu Connect uses the
Agent Communication Infrastructure (ACI)...”; update that sentence so it reads
"...to enable you to interact with your agents across different messaging
platforms."

Comment on lines +22 to +25
## Connect your agent brain

Novu Connect accepts two kinds of agent brains. You choose how you want to bring the intelligence.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Define “agent brain” before splitting it into types.

This term is non-standard and currently introduced without a direct definition. Add one sentence that defines it in Novu terms before listing managed vs custom options.

Suggested diff
 ## Connect your agent brain

+In this documentation, an **agent brain** means the runtime that receives conversation context from Novu and decides how to generate the next response.
+
 Novu Connect accepts two kinds of agent brains. You choose how you want to bring the intelligence.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## Connect your agent brain
Novu Connect accepts two kinds of agent brains. You choose how you want to bring the intelligence.
## Connect your agent brain
In this documentation, an **agent brain** means the runtime that receives conversation context from Novu and decides how to generate the next response.
Novu Connect accepts two kinds of agent brains. You choose how you want to bring the intelligence.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/docs/connect/index.mdx` around lines 22 - 25, Add a one-sentence
definition of "agent brain" in Novu terms immediately after the "## Connect your
agent brain" heading and before the sentence "Novu Connect accepts two kinds of
agent brains." The sentence should briefly define an agent brain as the service
or model that provides the agent's decision-making and context (e.g., "An agent
brain is the service or model that powers an agent's decision-making and
contextual understanding for handling user interactions."), then keep the
existing managed vs custom explanation intact.

```text
Create an engineering assistant agent that checks Linear and GitHub for open issues, pending PR reviews, and review requests. It summarizes what needs attention, flags blockers and stale tickets, and posts a short daily standup digest. It keeps responses concise and links back to the relevant Linear issue or GitHub pull request.
```
Novu will generate the agent for you, including its system prompt, tools, MCP servers, and skills based on your description.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Define “MCP” on first mention in this page.

This page uses “MCP” before defining it locally, which adds friction for first-time readers. Please expand first use to “Model Context Protocol (MCP)” and then use MCP afterward.

Also applies to: 68-68, 102-102, 115-117

🧰 Tools
🪛 GitHub Check: vale

[notice] 61-61: [vale] content/docs/connect/managed-agent/quickstart.mdx#L61
[Google.Acronyms] Spell out 'MCP', if it's unfamiliar to the audience.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@content/docs/connect/managed-agent/quickstart.mdx` at line 61, The page uses
the acronym "MCP" before defining it; update the first occurrence (the sentence
that currently reads "Novu will generate the agent for you, including its system
prompt, tools, MCP servers, and skills based on your description.") to "Model
Context Protocol (MCP)" on first mention and leave subsequent mentions as "MCP";
also update the other occurrences referenced (the instances around the current
text and the lines noted later) so they consistently use the full term on first
use and the acronym thereafter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants