Skip to content

■ SIGNALS // RADAR SIGNAL

the agent has an expense account, a memory bank, and a missing working directory

Paperclip tracks agent goals and costs; Hindsight documents retention and recall; Cursor fixes a plugin hook-path failure.

■ [!] ON THIS PAGE ▼

self.md radar — 2026-09-26

the agent has an expense account, a memory bank, and a missing working directory

Paperclip treats goals and spending as adjacent objects. Hindsight gives memory a three-verb API. Cursor’s plugin marketplace has a hook that failed because its directory changed.

1. Paperclip puts agent costs beside the assignment board

Paperclip is a Node.js server and React interface for a team of AI agents: give them goals, then track work and cost in one dashboard. Its test-drive commands name three routes—Anthropic, OpenAI/Codex, and OpenRouter/OpenCode—rather than hiding the provider behind a generic “agent” button.

The telemetry note is unusually bounded. It says issue content, prompts, file paths, and secrets do not leave the install; private repository references are salted and hashed. That is a policy statement, not a privacy audit. It is also part of what an operator accepts when the assignment board starts keeping score.

reading: Paperclip repository

2. Hindsight’s memory service has three verbs and 25-plus provider routes

Hindsight documents retain for writing a memory, recall for fetching it, and a chat wrapper that recalls before a model call then retains after it. The quick start runs a server on port 8888. Its embedded Python path says no server is required.

The provider list is the other half of the design: more than 25 hosted APIs, local runtimes, OpenAI-compatible endpoints, and gateways. The software makes the write and read operations explicit. It does not make the retention decision for you.

reading: Hindsight repository

3. Cursor fixes a plugin hook that assumed its own directory

The latest visible change in Cursor’s official plugin marketplace repository fixes a pstack hook that used ./hooks/... paths. Hooks do not necessarily start inside a plugin directory; in this case the result was exit 127. The repair points to CURSOR_PLUGIN_ROOT instead.

The repository packages skills, rules, and mcp.json definitions, and its catalogue includes plugins for SQL, feature flags, and trade previews or orders. That puts executable hooks beside actions with actual accounts and data behind them. A relative path is not a harmless detail when it decides whether the hook runs at all.

reading: Cursor plugins repository

left on the table

Screenpipe released app-v2.7.72 on September 25, but the public release record available today did not give enough detail to say what changed. It stays off the page rather than becoming a decorative fourth item.