[Use Case]: Cursor agent hooks for local EverOS memory

[Ayush7614]

Summary

Add a minimal use case under use-cases/cursor-agent-memory/ showing how to connect Cursor Agent hooks to the local EverOS 1.0 HTTP API for cross-session memory.

Memory behavior

• Recall at sessionStart: search EverOS with a workspace-based query and inject additional_context.
• Save on each agent stop: read the composer transcript and POST /api/v1/memory/add for the latest turn.
• Extract on sessionEnd: POST /api/v1/memory/flush so the session becomes durable Markdown-backed memory.

Stack and dependencies

• Cursor hooks (Python 3.12+, stdlib HTTP client)
• Local EverOS server (/api/v1/memory/add, /flush, /search)
• No committed secrets; .env.example only

Run path

See use-cases/cursor-agent-memory/README.md — run ./install.sh, configure .env, start everos server start, enable hooks in Cursor.

Contribution checklist

• README with setup instructions
• No secrets, generated output, dependency folders, or image files
• .env.example included