Comparison

A · Cursor rules · novuhq/novu B · AGENTS.md · novuhq/novu

What each file covers, counted
Dimension	Only in A	Only in B	Overlap
Sections	1	9	0%
Commands	1	2	0%
Section tags	0	3	0%

What each file covers

Sections

0 shared · 1 only in A · 9 only in B

− `minimumReleaseAge` and `minimumReleaseAgeExclude`
+ AGENTS.md
+ Cursor Cloud specific instructions
+ Build
+ AI Boundaries
+ Always
+ Ask First
+ Never
+ Developer-local agent config
+ Novu Distribution

Commands

0 shared · 1 only in A · 2 only in B

− pnpm-workspace.yaml
+ pnpm setup:agent
+ pnpm build

Section tags

0 shared · 0 only in A · 3 only in B

+ build
+ do-not
+ agent-behaviour

Line diff

+40 added−7 removed4 unchanged9.1% identical

novuhq/novu · .cursor/rules/pnpm-release-age.mdc

@@ −1 @@

1---

2description: pnpm minimumReleaseAge — never bypass for fresh publishes

3alwaysApply: true

4---

6### `minimumReleaseAge` and `minimumReleaseAgeExclude`

8Do not add packages to `minimumReleaseAgeExclude` in `pnpm-workspace.yaml` to work around the configured `minimumReleaseAge`. That policy applies to every dependency, not only specific names.

10If a version was published more recently than `minimumReleaseAge` allows, do not install or bump to it until it is old enough. For urgent security fixes, wait for the window, or resolve to a patched release that already satisfies the age rule—without exempting the package from minimum release age.

novuhq/novu · AGENTS.md

@@ +1 @@

1# AGENTS.md

3## Cursor Cloud specific instructions

5`pnpm setup:agent` has already been run. Do not run it again. The environment is fully configured: dependencies installed, enterprise packages linked, project built, `.env` files in place, Docker services running, and a default user/org seeded. The dashboard auto signs in the pre-seeded agent user when opened in the browser (no manual login unless auto sign-in fails).

7## Build

9Run `pnpm build` after changes to `packages/` or `enterprise/`. Direct changes to `apps/` do not require a rebuild.

11## AI Boundaries

13### Always

14- Work within: `apps/api`, `apps/dashboard`, `apps/worker`, `apps/ws`

15- Use shared packages: `packages/shared`, `packages/framework`, `packages/js`, `packages/react`

16- Follow `libs/dal` for data access, `libs/application-generic` for business logic

18### Ask First

19- Before creating new UI components not in `apps/dashboard/src/components/`

20- Before adding npm dependencies

21- Before modifying MongoDB models, ClickHouse table definitions, or anything in `enterprise/` or `packages/providers/`

23### Never

24- Inactive apps — do not touch, unless monorepo wide refactor: `apps/webhook`

25- Auto-generated — never edit: `libs/internal-sdk`

26- UI: reuse existing Radix/shadcn components only; do not copy patterns from `playground/` into production code

27- If doing a monorepo wide refactor, you can touch the read only, but only when necessary.

30## Developer-local agent config

32If a **`.agents-local/`** directory exists in your working copy, read **`.agents-local/README.md`** first for personal, git-ignored agent configuration, skills and rules. Absence of the directory is normal.

34## Novu Distribution

35Novu is distributed in 3 modes, Community Edition, Enterprise Cloud Edition, and On-Prem Enterprise Edition.

37When making changes targeted to the Enterprise distribution, we need to make sure that the changes are not breaking the Community edition, and are properly gated behind a flag, or the novu enterpise env variables. Similarly when some changes are only targeting the Cloud, self-hosted on prem should not be affected.

39

40

41

42

43

@@ −1 +1 @@

1−---

2−description: pnpm minimumReleaseAge — never bypass for fresh publishes

3−alwaysApply: true

4−---

1+# AGENTS.md

6−### `minimumReleaseAge` and `minimumReleaseAgeExclude`

3+## Cursor Cloud specific instructions

8−Do not add packages to `minimumReleaseAgeExclude` in `pnpm-workspace.yaml` to work around the configured `minimumReleaseAge`. That policy applies to every dependency, not only specific names.

5+`pnpm setup:agent` has already been run. Do not run it again. The environment is fully configured: dependencies installed, enterprise packages linked, project built, `.env` files in place, Docker services running, and a default user/org seeded. The dashboard auto signs in the pre-seeded agent user when opened in the browser (no manual login unless auto sign-in fails).

10−If a version was published more recently than `minimumReleaseAge` allows, do not install or bump to it until it is old enough. For urgent security fixes, wait for the window, or resolve to a patched release that already satisfies the age rule—without exempting the package from minimum release age.

7+## Build

9+Run `pnpm build` after changes to `packages/` or `enterprise/`. Direct changes to `apps/` do not require a rebuild.

10+

11+## AI Boundaries

12+

13+### Always

14+- Work within: `apps/api`, `apps/dashboard`, `apps/worker`, `apps/ws`

15+- Use shared packages: `packages/shared`, `packages/framework`, `packages/js`, `packages/react`

16+- Follow `libs/dal` for data access, `libs/application-generic` for business logic

17+

18+### Ask First

19+- Before creating new UI components not in `apps/dashboard/src/components/`

20+- Before adding npm dependencies

21+- Before modifying MongoDB models, ClickHouse table definitions, or anything in `enterprise/` or `packages/providers/`

22+

23+### Never

24+- Inactive apps — do not touch, unless monorepo wide refactor: `apps/webhook`

25+- Auto-generated — never edit: `libs/internal-sdk`

26+- UI: reuse existing Radix/shadcn components only; do not copy patterns from `playground/` into production code

27+- If doing a monorepo wide refactor, you can touch the read only, but only when necessary.

28+

29+

30+## Developer-local agent config

31+

32+If a **`.agents-local/`** directory exists in your working copy, read **`.agents-local/README.md`** first for personal, git-ignored agent configuration, skills and rules. Absence of the directory is normal.

33+

34+## Novu Distribution

35+Novu is distributed in 3 modes, Community Edition, Enterprise Cloud Edition, and On-Prem Enterprise Edition.

36+

37+When making changes targeted to the Enterprise distribution, we need to make sure that the changes are not breaking the Community edition, and are properly gated behind a flag, or the novu enterpise env variables. Similarly when some changes are only targeting the Cloud, self-hosted on prem should not be affected.

38+

39+

40+

41+

42+

43+

1144