docs(website): refresh agent-memory.dev for v0.9.15+#415
Merged
Conversation
Drift accumulated across the website from v0.9.0 through v0.9.15. Each section caught up: CommandCenter: - "iii CONSOLE · OPTIONAL" → "iii CONSOLE · FIRST-CLASS". User pushback: the console gives engine-level visibility (workers, functions, queues, traces) and is now installed inline by the agentmemory CLI on first run from v0.9.16. Not optional. - Bullet "49 HTTP TRIGGERS" → "107 HTTP ENDPOINTS" to match generated-meta.json restEndpoints count. Dropped the stale "33 REGISTERED FUNCTIONS" subhead. - Section lede now mentions both UIs are first-class + inline- installed. Compare: - MCP TOOLS our column 44 → 51 (matches generated-meta.json). - New REST ENDPOINTS row (107) — competitors don't ship a REST shape per their docs, so dashes for mem0/letta/cognee. - New NATIVE PLUGINS row listing the 6 first-party agents + Cursor/Gemini CLI. Agents: - FEATURED expanded from 4 to 6 (added pi + OpenHuman). Codex CLI pitch updated to "6 hooks + MCP · native plugin" reflecting the hooks addition in PR #383. - Section title "FOUR FIRST-PARTY" → "SIX FIRST-PARTY". - Section lede now mentions `agentmemory connect <agent>` (shipped in v0.9.15 PR #402). Hero: - "START IN 60 SECONDS" CTA → "START IN 30 SECONDS". Cold install + engine spawn measured 8-12s on v0.9.15 with the native binary path; 60s was the v0.9.0-era Docker-first claim. generated-meta.json regenerated by the build (auto-derive rule). Website build clean.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✅ Files skipped from review due to trivial changes (3)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThis PR updates website marketing copy and components: adds Pi and OpenHuman to featured agents and tweaks Codex CLI, repositions the console as first‑class, updates the comparison table, adds a new FeaturedIn section with styles and image host allowlist changes, shortens the Hero CTA to 30 seconds, and refreshes the build timestamp. ChangesWebsite Marketing Refresh
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 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 `@website/components/CommandCenter.tsx`:
- Line 48: The displayed hardcoded string in the CommandCenter component ("107
HTTP ENDPOINTS · REPLAY ANY REST CALL") is out of sync with the source-of-truth
`restEndpoints` value in website/lib/generated-meta.json; update the component
to use the correct count (121) or, better, import/read `generated-meta.json` and
render `${meta.restEndpoints} HTTP ENDPOINTS · REPLAY ANY REST CALL` inside the
CommandCenter component so the UI always reflects the metadata source of truth.
In `@website/components/Compare.tsx`:
- Line 9: The "NATIVE PLUGINS" row in Compare.tsx is inconsistent: the count "6"
does not match the eight names in the parenthesized list inside the array entry
["NATIVE PLUGINS", "6
(Claude/Codex/Cursor/Gemini/OpenClaw/Hermes/pi/OpenHuman)", "—", "—", "—"].
Update this entry so the numeric count matches the list — either change the "6"
to "8" or remove two names from the parenthesis to make it six — ensuring the
array element string and the displayed count are consistent.
- Line 6: The "REST ENDPOINTS" table row is hardcoded to "107" and thus out of
sync with website/lib/generated-meta.json (restEndpoints: 121); update the
Compare component to read the live value from the generated metadata instead of
the literal "107": import or require the generated-meta.json (or its exported
restEndpoints) in the Compare.tsx component and replace the hardcoded array
entry ["REST ENDPOINTS", "107", "—", "—", "—"] with a dynamic value that uses
the imported restEndpoints (ensuring proper toString/formatting where the table
expects a string) so the table always reflects generated-meta.json.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8f8ee63e-eae6-4d35-aaca-b859a4ee38fc
📒 Files selected for processing (5)
website/components/Agents.tsxwebsite/components/CommandCenter.tsxwebsite/components/Compare.tsxwebsite/components/Hero.tsxwebsite/lib/generated-meta.json
Wedges between Hero and Stats. Three text-cells in a 3-col row (1-col on mobile), each links to the source article. Matches the existing brutalist mono aesthetic — no logo files, no marquee animation, no JS. Border + small ↗ glyph on each card; gold border on hover. Sources chosen for brand authority + independence: - AlphaSignal (180K technical subscribers) → alphasignalai.substack.com/p/how-agentmemory-works-and-how-to - Agentic AI Foundation (Linux Foundation backed) → aaif.io - Trendshift "NEW 2026 · Position #19" → trendshift.io/repositories/25123 Static, server-rendered, no client bundle impact.
Replaced text-only treatment with actual brand marks: - AlphaSignal — github.com/Alpha-Signal org avatar (verified) https://avatars.githubusercontent.com/u/64016073?s=200&v=4 - Agentic AI Foundation — aaif.io's own favicon PNG (verified by fetching their site) - Trendshift — their official badge endpoint trendshift.io/api/badge/repositories/25123 — bakes the repo's live star + position count into the image, so the cell tracks the Trendshift state automatically Layout split: AlphaSignal + AAIF render logo-left / text-right with ↗ arrow. Trendshift renders centered with the full badge image (it's already a wide brand mark with the rank + stars baked in, so making it text-bound looks cramped). next.config.ts adds the three new image hosts to remotePatterns (aaif.io, trendshift.io, raw.githubusercontent.com). Existing unoptimized={true} per image so we don't proxy through Vercel's optimizer. Build clean. No new deps.
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 `@website/components/FeaturedIn.module.css`:
- Around line 62-70: The .cellBadge CSS rule contains an invalid/unused property
for a flex container—remove the grid-only property `grid-template-columns:
none;` from the .cellBadge rule so the flex layout uses only relevant properties
(display: flex, flex-direction, align-items, justify-content, gap, padding).
- Around line 43-61: Add a keyboard focus-visible state for the .cell element so
tabbing users get a clear indicator: implement a .cell:focus-visible rule that
mirrors or complements the .cell:hover visual cues (e.g., border-color:
var(--gold), transform: translateY(-1px) and a visible focus outline or
box-shadow) to ensure focus is perceivable and meets WCAG 2.4.7; update the
.cell selector to include focusable semantics if necessary (e.g., for anchor or
button usage) and ensure the focus style has sufficient contrast against
var(--iron)/#16161a.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: d00de811-5d8b-4626-9516-ba6893125186
📒 Files selected for processing (4)
website/components/FeaturedIn.module.csswebsite/components/FeaturedIn.tsxwebsite/lib/generated-meta.jsonwebsite/next.config.ts
✅ Files skipped from review due to trivial changes (3)
- website/next.config.ts
- website/components/FeaturedIn.tsx
- website/lib/generated-meta.json
User pushed the actual Agentic AI Foundation wordmark — 838x203 PNG on transparent background, black artwork. Dropped the favicon and self-hosted the wordmark at /featured/aaif-logo.png so the brand reads cleanly on the dark cell. Rendered as a badge-style cell (centered, wide-form) like Trendshift, with a `filter: invert(1) brightness(1.05)` so the black artwork inverts to white-on-dark and matches the site palette without shipping a second asset. Grid template balanced: 1fr / 1.3fr / 1fr — gives AAIF the extra horizontal room its wordmark needs while keeping AlphaSignal and Trendshift consistent on either side. Max width bumped to 1000px. `badgeImg` got `object-fit: contain` and an explicit `max-height` so the AAIF + Trendshift badges sit at the same vertical baseline.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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 `@website/components/FeaturedIn.tsx`:
- Around line 52-58: In the FeaturedIn component update the external anchor
elements that open in a new tab (the anchors created inside the map/iteration
using key={it.name} and the other anchor for the sponsor/badge) to add
"noreferrer" to their rel attributes; change rel="noopener" to rel="noopener
noreferrer" on the <a> elements that have target="_blank" so both occurrences
(the anchor using key={it.name} and the other badge link) include rel="noopener
noreferrer" to prevent referrer leakage.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 445ef831-3bc9-4d2e-a0f0-e79fc92a42fa
⛔ Files ignored due to path filters (1)
website/public/featured/aaif-logo.pngis excluded by!**/*.png
📒 Files selected for processing (3)
website/components/FeaturedIn.module.csswebsite/components/FeaturedIn.tsxwebsite/lib/generated-meta.json
🚧 Files skipped from review as they are similar to previous changes (2)
- website/lib/generated-meta.json
- website/components/FeaturedIn.module.css
Comment on lines
+52
to
+58
| <a | ||
| key={it.name} | ||
| className={`${styles.cell} ${styles.cellBadge}`} | ||
| href={it.href} | ||
| target="_blank" | ||
| rel="noopener" | ||
| aria-label={`${it.name} — ${it.sub}`} |
There was a problem hiding this comment.
Add noreferrer to external _blank links.
Line 57 and Line 80 currently use rel="noopener" only. Add noreferrer as well to prevent referrer leakage on third-party outbound links.
Suggested patch
- rel="noopener"
+ rel="noopener noreferrer"
...
- rel="noopener"
+ rel="noopener noreferrer"Also applies to: 75-81
🤖 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 `@website/components/FeaturedIn.tsx` around lines 52 - 58, In the FeaturedIn
component update the external anchor elements that open in a new tab (the
anchors created inside the map/iteration using key={it.name} and the other
anchor for the sponsor/badge) to add "noreferrer" to their rel attributes;
change rel="noopener" to rel="noopener noreferrer" on the <a> elements that have
target="_blank" so both occurrences (the anchor using key={it.name} and the
other badge link) include rel="noopener noreferrer" to prevent referrer leakage.
Five findings, all valid against the branch: 1. CommandCenter line 48 hardcoded "107 HTTP ENDPOINTS" but website/lib/generated-meta.json reports restEndpoints: 121. Bumped to 121. The meta file is the source of truth (auto-derived from src/triggers/api.ts at build via scripts/derive-meta.js). 2. Compare.tsx REST ENDPOINTS row same drift: "107" → "121". 3. Compare.tsx NATIVE PLUGINS row claimed "6" in the label but the parenthesized list had 8 names (Cursor + Gemini included). Per README: those two are MCP-server tier, not native plugin. List trimmed to the actual 6 native-plugin agents: Claude/Codex/OpenClaw/Hermes/pi/OpenHuman. 4. FeaturedIn.module.css .cell had :hover only — keyboard users tabbing through saw no focus indicator (WCAG 2.4.7). Added :focus-visible with gold border + outline. 5. .cellBadge declared `grid-template-columns: none` while using display: flex. Dead property removed.
This was referenced May 15, 2026
rohitg00
added a commit
that referenced
this pull request
May 15, 2026
Patch bump per the established rule: additive surface only, no breaks to MemoryProvider trait, exported types, or default behaviour. New top-level subcommands (`--reset` already shipped 0.9.15, no new commands here) are opt-in. PRs included since v0.9.15: #408 — onboarding wires selected agents inline + memory-share callout #409 — clarify MCP is opt-in (REST primary) #410 — 5-port ready panel, iii console install, global-install prompt #411 — splash banner rerender + README install hoist + npx caveat #415 — agent-memory.dev refresh (FeaturedIn bar + Agents/Compare/ CommandCenter/Hero updates) Files bumped (9): package.json, packages/mcp/package.json, plugin/.claude-plugin/plugin.json, plugin/.codex-plugin/plugin.json, src/version.ts, src/types.ts, src/functions/export-import.ts, test/export-import.test.ts, CHANGELOG.md
This was referenced May 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refresh the marketing site to reflect what v0.9.15 actually ships (and what v0.9.16 is about to). The four website component changes from PR #411 weren't squash-merged with the rest, so doing them here in a focused PR.
Changes
CommandCenter —
iii CONSOLE · OPTIONAL→iii CONSOLE · FIRST-CLASS. The console gives engine-level visibility (workers, functions, queues, traces); v0.9.16 installs it inline on first run. Bullet counts updated: dropped stale33 functions,49 triggers→107 HTTP endpoints(matchesgenerated-meta.json).Compare —
MCP TOOLSrow: 44 → 51. NewREST ENDPOINTSrow (107) andNATIVE PLUGINSrow (lists 6 first-party agents).Agents — featured grid expanded from 4 to 6 (added pi + OpenHuman). Codex CLI sub updated to
NATIVE PLUGIN(it has 6 hooks now, not just MCP). Section titleFOUR FIRST-PARTY→SIX FIRST-PARTY. Lede mentionsagentmemory connect <agent>.Hero —
START IN 60 SECONDSCTA →START IN 30 SECONDS. Cold install + engine spawn was measured at 8-12s on v0.9.15 via the native binary path; the 60s figure was the v0.9.0-era Docker-first claim.Test plan
cd website && npm run build— cleanSummary by CodeRabbit
New Features
Documentation
Style