
Security News
Lovable’s OJ Rewrites Vite’s Dev Server in Rust as AI Lowers the Cost of Forking Open Source
Lovable’s OJ rewrites Vite’s dev server in Rust, reducing memory use and preview times as AI lowers the cost of open source reimplementation.
Agent memory that cannot bloat. The default MCP memory server grows unbounded - users report 80k-token memory files billed on every request. STICKY caps it: ten active notes, the oldest tumbles to a free archive. Local, no cloud.
A board your coding agent can write to — and you can see.
Your agent forgets between sessions. The usual fix is a CLAUDE.md that grows until it's a
thousand lines of stale rules nobody deletes, quietly costing you tokens on every request.
STICKY holds ten active notes. When the eleventh arrives, the oldest one tumbles to the archive on its own. Nothing to prune, nothing to garden.
npx sticky-mcp
That's it. The board opens in your browser. No account, no cloud, no config.
claude mcp add sticky -- npx sticky-mcp-server
Cursor, Cline, Windsurf and anything else that speaks MCP work the same way — point them at
npx sticky-mcp-server.
Or add it to your MCP config by hand:
{
"mcpServers": {
"sticky": {
"command": "npx",
"args": ["-y", "sticky-mcp-server"]
}
}
}
sticky-mcp-servertakes no flags on purpose. Some CLIs — Claude Code among them — read-yand--mcpas their own options and never pass them through, so a command with nothing after it is the only one that works everywhere.
Your agent gets two tools:
post_sticky — pin a decision, a constraint, or where the work pausedread_active_stickies — read the board at the start of a session| what it holds | reaches the agent | |
|---|---|---|
| Pinned | permanent rules — "use C# 12", "never touch migrations by hand" | always |
| Active | current decisions and where work stopped | always, newest 10 |
| Archive | whatever tumbled off | never — zero tokens |
Drag a note between columns. Drop it on Pinned and it becomes a permanent rule. Drop it on Archive and it stops reaching the agent immediately. Double-click to edit, click the cross to bin a bad assumption.
The board updates live as your agent posts — you watch it think.
Being precise, because a promise that isn't quite true is worse than no promise:
So the agent's context stays bounded at roughly 25 notes, permanently, no matter how long you work.
The board is a SQLite file at ~/.sticky/store.db. The web server binds to 127.0.0.1 and
nothing else. There is no telemetry, no analytics, and no network code in this package beyond
the local server itself.
npx sticky-mcp open the board
npx sticky-mcp --mcp run as an MCP server (agents launch this)
--cap <n> active notes before the oldest tumbles (default 10)
--port <n> board port (default 7317)
--db <path> where the board lives (default ~/.sticky/store.db)
--no-open start without opening a browser
Want it floating beside your editor? chrome --app=http://localhost:7317
Node 22.5 or newer — STICKY uses Node's built-in SQLite, so there's nothing to compile and no native modules to install.
MIT licensed. Built by Juvina.
FAQs
Agent memory that cannot bloat. The default MCP memory server grows unbounded - users report 80k-token memory files billed on every request. STICKY caps it: ten active notes, the oldest tumbles to a free archive. Local, no cloud.
We found that sticky-mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.

Security News
Lovable’s OJ rewrites Vite’s dev server in Rust, reducing memory use and preview times as AI lowers the cost of open source reimplementation.

Security News
It has been one year since Shai-Hulud made its first appearance on npm.

Research
/Security News
Operators behind PolinRider used a compromised GitHub account to plant malware in four development versions of a Packagist package with 700,000+ downloads.