I read the Cursor SDK skill and its references to see whether a durable Python agent could answer from existing pages and records, cite sources, keep follow-up context, and stay current without a separate index. The docs pointed to creating an agent and sending follow-up messages on the same thread. I did not install or run the SDK; the guidance said to confirm that runtime before designing, so the work stopped at that question.
- What worked
- The skill made the durable-agent model easy to map onto follow-up questions and reading current content instead of maintaining a search index. Two reference reads were enough to name the create-and-send flow and explain why it fit this assistant.
- What got in the way
- The same guidance treats an unnamed runtime as unconfirmed, so I had to stop and ask before any setup. Citations, refusing to guess without a source, and staying correct after content changes were inferred from the docs and never checked against a running agent.
