Weekly Digest & Stale Nudges

Every Sunday at 6:00 PM UTC, NeuralRepo sends Pro users a weekly digest email summarizing idea activity. A separate Monday check nudges you (on any plan) about ideas that have been sitting untouched in captured.

What the Digest Contains

Without a BYOK Key

A stats summary:

• New ideas this week — how many ideas you captured in the last 7 days.
• Pending duplicates — potential duplicates waiting for review.
• Stale ideas — ideas stuck in captured past your stale threshold, with a nudge to move them forward or shelve them.
• Total ideas — your active idea count.

With a BYOK Key

The same data, written up as a short narrative summary by your configured AI provider — including a specific suggestion based on the week’s activity (e.g., which stale ideas to revisit). If the AI call fails, the digest falls back to the stats summary.

Tip

The AI-written digest requires a configured BYOK key. See the BYOK setup guide for instructions.

Note

The digest is only sent when there is something to report — if a week has no new ideas, no pending duplicates, and no stale ideas, no email goes out.

Stale Idea Nudges

Separately from the digest, NeuralRepo checks every Monday at 9:00 AM UTC for ideas that have been stuck in captured — created but never explored, built, or shelved. If you have any, you get a short email listing them with how long each has been untouched.

• Available on all plans (the digest is Pro-only).
• Sent at most once a month per user, even though the check runs weekly — an ignored nudge won’t repeat every Monday.
• An idea counts as stale when it is in captured status, not archived, and hasn’t been updated for more than your stale threshold (default: 30 days). Editing an idea resets the clock.

Delivery Schedule

Event	Schedule	Cron Expression
Weekly digest (Pro)	Sunday 6:00 PM UTC	0 18 * * SUN
Stale idea nudge check	Monday 9:00 AM UTC	0 9 * * 1

Both emails go to the address associated with your NeuralRepo account.

Configuration

Manage both emails from Settings > Notifications in the web dashboard:

• Weekly digest email — on by default for Pro accounts; toggle off to opt out.
• Stale idea nudges — on by default for all accounts; toggle off to opt out.
• Stale threshold — how many days before a captured idea counts as stale (default: 30, range 7–180). Applies to both the nudge emails and the digest’s stale section.
• Preferred AI provider — which BYOK provider writes the digest summary (in Settings > AI Providers).

Testing the Digest

You can trigger a test digest at any time without waiting for Sunday (it sends even if you’ve toggled the weekly digest off):

curl -X POST https://neuralrepo.com/api/v1/user/test-digest \
  -H "X-API-Key: nrp_your_key_here"

Response 200 OK:

{
  "success": true,
  "content": "..."
}

The content field contains the rendered digest content that was sent.

How It Works

Both emails are generated by Cloudflare Workers Cron Triggers:

1. The Sunday cron queries Pro users who haven’t opted out of the digest.
2. For each user, it gathers the week’s data: new ideas, pending duplicates, stale ideas, and totals.
3. If the user has a BYOK key, it asks the AI provider to write the summary; otherwise it formats the stats directly.
4. The digest is sent as an HTML email.

The Monday cron checks every user (any plan) who hasn’t opted out of nudges, skips anyone nudged within the last month, and emails a list of their stale ideas if there are any.

Example Digest

A typical AI-written digest looks like this:

You captured 5 new ideas this week, with a cluster forming around CLI improvements — that’s your most active area this month.

There are 2 potential duplicates waiting for review, and 3 ideas have been sitting in “captured” for over 30 days, including “GraphQL schema generator” and “Redis cache layer.” Consider moving them to exploring or shelving them to clear the deck.

Your repo now holds 47 active ideas. Nice momentum — keep it up.

Next Steps

BYOK AI Providers Configure your AI key to unlock the AI-written digest.

Status Workflow Understand the idea lifecycle and how statuses affect stale detection.