Skip to content

feat(website): show the developer experience and the performance work - #1715

Merged
rohitg00 merged 1 commit into
mainfrom
feat/website-perf-devex
Nov 9, 2026
Merged

rohitg00 merged 1 commit into
mainfrom
feat/website-perf-devex

Conversation

@rohitg00

@rohitg00 rohitg00 commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

The homepage showed recall and local-first, but not how little it takes to run agentmemory or the scale work in 0.9.31 to 0.9.33. This adds two homepage sections and corrects one FAQ answer.

Developer experience (#devex, after Use cases)

  • Terminal figure with the real CLI commands: start, connect, demo --serve, doctor, status. Each output line matches the CLI help in src/cli.ts.
  • The stack that the first command starts: iii engine on 127.0.0.1:49134, state, http (REST :3111) and agentmemory (viewer :3113) workers, from src/cli/compose-project.ts and src/cli/compose-control.ts.
  • Facts: no key needed (provider opt-in since fix(plugin): address the directory review on data capture, providers and listing #1664), background service recipes (docs deployment page), agentmemory remove keeps data by default.

Performance (#performance, before Benchmarks)

Other

  • FAQ "Do I need an API key?": a key alone no longer enables LLM features, so the answer names AGENTMEMORY_LLM_PROVIDER.
  • llms-full.txt gains matching Operate and Performance sections.

Verification

  • npm run build in website/ passes.
  • next start with Playwright: both sections in light and dark, at 1440 px and 390 px. No element offscreen and no horizontal page overflow.
  • Screenshots were reviewed locally: desktop and mobile, light and dark, for each section.

Summary by CodeRabbit

  • New Features
    • Added a Runtime section describing installation, agent connection, and deployment options.
    • Added a Scale section comparing memory-reading approaches and summarizing performance gains.
  • Documentation
    • Expanded the reference guide with operation commands, provider settings, deployment recipes, and performance details.
    • Clarified that recall can work without an API key, while LLM consolidation requires a configured provider and key.

Add a developer experience section with a terminal session of the real
CLI commands and the Worker Compose stack the first command starts, and
a performance section that shows the paged state read path against the
old single-frame read, plus sourced gains from 0.9.31 to 0.9.33. The
API key FAQ now says a provider must be named, as it is since 0.9.32,
and llms-full.txt carries both sections.
@vercel

vercel Bot commented Nov 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
agentmemory Ready Ready Preview Nov 9, 2026 5:07am UTC

Request Review

@coderabbitai

coderabbitai Bot commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

Caution

Review failed

The pull request is closed.

Walkthrough

The homepage adds Runtime and Scale sections. The site’s full-text content gains operational and performance information, and the API-key FAQ is updated.

Changes: Homepage and Site Documentation

Layer / File(s) Summary
Runtime section
website/components/site/Runtime.tsx, website/components/site/Runtime.module.css, website/app/page.tsx
The homepage adds a Runtime section with a terminal session, a four-layer stack, and informational facts. Styles include responsive layouts, entrance animations, and reduced-motion handling.
Scale comparison section
website/components/site/Scale.tsx, website/components/site/Scale.module.css
The Scale section compares before-and-after flows and lists six versioned performance gains with links. Styles provide responsive layouts and step animations.
Operational and performance information
website/lib/llms.ts, website/lib/site.ts
The full-text content documents operational commands, provider conditions, deployment recipes, and performance details. The FAQ clarifies keyless recall and provider-key requirements.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Other

Possibly related issues

  • rohitg00/agentmemory#1579 — The Scale section describes paged state reads addressing the reported frame-limit behavior, but it does not describe changes to endpoint responses or provenance lists.
  • rohitg00/agentmemory#1710 — The Scale section describes paged state reads related to the reported payload limit, but does not state that the migration discovery read is resolved.

Possibly related PRs

  • rohitg00/agentmemory#1641 — The Runtime section describes Windows support for starting Worker Compose, which is related to the Windows startup path changed in that PR.
Merge Risk: Low · up to 254b8

The homepage has bounded accessibility and documentation issues: screen readers cannot navigate the terminal commands, two performance claims need qualification, and citations need small navigation and styling fixes. These are low-risk corrections rather than blockers to application operation.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

@devin-ai-integration devin-ai-integration 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.

Devin Review found 3 potential issues.

Devin Review

Comment thread website/app/page.tsx
Comment on lines +11 to +12
import { Runtime } from "@/components/site/Runtime";
import { Scale } from "@/components/site/Scale";

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.

🟡 Missing sign-off blocks PR merge

The current commit lacks a Signed-off-by trailer. The required DCO check blocks this PR from merging.

Learn more

The repository requires a Signed-off-by trailer on every commit, and the current commit has none. This cannot be fixed by changing source lines.

Example: git log -1 --format=%B shows the feature commit message without a Signed-off-by: line; the DCO gate rejects it.

Recommended fix: Add a valid author sign-off to the commit while following the repository's history and review-feedback policies; ensure every commit in the PR passes DCO.

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

Comment on lines +5 to +10
const SESSION = [
{ cmd: INSTALL_CMD, out: "installs the pinned iii engine on macOS, Linux or Windows, then starts Worker Compose" },
{ cmd: "agentmemory connect claude-code", out: "wires MCP and capture hooks into the agent you pick" },
{ cmd: "agentmemory demo --serve", out: "seeds sample sessions, shows recall, then stops the server it started" },
{ cmd: "agentmemory doctor", out: "finds config problems and offers a fix for each one" },
{ cmd: "agentmemory status", out: "health, memory count, feature flags and anything that needs attention" },

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.

🔍 Terminal sequence needs a separate CLI install

On a fresh machine, npx runs the first command without putting agentmemory on PATH. The later commands in the displayed session require a separate installation, as does the existing Install section.

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

Comment on lines +32 to +34
key: "undo",
text: "agentmemory remove shows a plan, unwires every agent it connected and keeps your memory data unless you say otherwise.",
},

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.

🔍 Undo guidance skips the required stop

After the displayed start command, agentmemory remove refuses to run while Worker Compose owns the runtime. The CLI requires agentmemory stop first; otherwise users never see the promised plan.

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

@rohitg00
rohitg00 merged commit 5634bc5 into main Nov 9, 2026
3 checks passed
@rohitg00
rohitg00 deleted the feat/website-perf-devex branch November 9, 2026 05:11

This branch was successfully deployed

1 active deployment
Preview — 254b8fee Deployed Nov 9, 2026 by vercel[bot]
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.

1 participant