Skip to content

Releases: cppalliance/cppa-cursor-browser

v0.1.0

05 Jun 16:08
@bradjin8 bradjin8
v0.1.0
937dc91
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
v0.1.0 Latest
Latest

First tagged release of cppa-cursor-browser — browse, search, and export Cursor AI chat histories from local Cursor storage.

Highlights

  • Web UI — workspace browsing and search, syntax-highlighted code blocks, dark/light mode, bookmarkable URLs
  • Export — Markdown, HTML, PDF, JSON, and CSV from the UI; CLI cursor-chat-export with zip or per-file Markdown and incremental --since last
  • Cursor CLI agent sessions — read and export ~/.cursor/chats/ when the IDE DB is absent
  • Performance — lazy-load workspace UI, summary-only tab API, per-conversation loads, mtime-keyed disk cache (#84)
  • Packaging — pyproject.toml / hatchling, CI on Linux/macOS/Windows, optional Windows desktop .exe
  • Quality — typed SQLite models, structured logging, security hardening (path traversal, DOMPurify, debug off by default)

Workspace API

The workspace page loads the sidebar with GET /api/workspaces/<id>/tabs?summary=1 (metadata only). Each conversation is fetched on demand via GET /api/workspaces/<id>/tabs/<composer_id>. The full GET /api/workspaces/<id>/tabs endpoint (all tabs assembled in one response) remains available for backward-compatible API clients. Bulk export and full-text search use separate routes (POST /api/export, GET /api/search), not the full tabs endpoint.

Using full /tabs without ?summary=1 from the workspace UI on page load is deprecated in the changelog (planned removal post-1.0); the UI no longer does this.

Pre-1.0 stability

While at 0.x.y, breaking changes may land in minor releases. See Versioning and API deprecation policy.

Full changelog: CHANGELOG.md — 0.1.0

Assets 2
Loading