Recent updates.
User-visible highlights. The full technical changelog — with file paths, root causes, and rollback notes — lives in the repository.
August 2026
2026-08- Dependency health for project repositories
Projects with a bound GitHub repository get a Dependencies tab and an overview card: the repo's package.json is scanned against the npm registry and every package is classified as up-to-date, patch, minor, or major behind.
- Automatic daily scans with configurable alerts
Bound repositories are re-scanned automatically every day. Project owners get a notification per severity level while issues remain — and each level (major / minor / patch) has its own reminder cadence in Project Settings → Dependency alerts: off, daily, weekly, or monthly.
- Export outdated dependencies
The Dependencies page can copy or download the current issue list — every major, minor, and patch update pending, worst-first — as JSON or CSV.
- Project chat with @-mentions
Every project has a realtime Chat tab for its members. Type @ to mention a teammate (they get a notification), and attach references to the project’s tasks, notes, checklists, flows, sprints, and milestones as clickable chips.
- Projects page: list view, search, and pinning
A sortable list view is now the default on the Projects page, with a cards/list switcher, name search, and state filters. Projects can be pinned to keep them on top for the whole team.
- Notion-style editor for notes
The note page swaps its markdown textarea for a block editor — slash-menu blocks, drag handles, inline formatting — while notes stay markdown underneath, so VS Code sync is untouched. Notes are also protected by check-out locking so two people can’t silently overwrite each other.
- Marketing pages
caspiantools.com has a real public-facing site — home, features, pricing, about, privacy, terms, changelog, and this support page. Logged-out visitors land here instead of being bounced straight to the sign-in page.
May 2026
2026-05- Per-note sync badge
Every note now shows a small Synced check on its card and detail header, so you can tell at a glance that your edits made it to the cloud.
- Project pill on task cards and rows
Tasks attributed to a project show the project name on the kanban card and the list row. Tasks without a project show nothing, as before.
- Cloud Functions on Node 22
Backend functions upgraded to Node 22 with firebase-functions v7 and firebase-admin v13. No user-visible behaviour change; this is a runtime refresh ahead of the Node 20 deprecation.
April 2026
2026-04- Assignee picker scoped to the project
On a task with a project, the assignee dropdown lists only that project's members. On a task without a project, it lists workspace members.
- Breadcrumbs and context-aware Back
Every detail page (task, sprint, milestone, note) renders a chain of breadcrumbs derived from the entity itself, plus a Back arrow that honours where you came from.
- Notes list: search, filters, and bulk operations
Fuzzy search across title, tags, and body. Tag and project filters. Multi-select with bulk pin, bulk-set-project, and bulk delete.
- Note detail: project picker
You can now attribute a note to a project — or clear its project — from the note detail page, not just from bulk actions.
- Pair-time default project for the VS Code extension
When you pair Caspian-Taskmaster, you can pick a default Caspian Project so new tasks created in the editor land in that project automatically.
- Web pushes to GitHub directly
Tasks attributed to a project with a primary repo now push to GitHub from the web using your own GitHub OAuth token, in addition to the extension's push path.
March 2026
2026-03- Projects
A new work-boundary container with its own members, tasks, notes, sprints, milestones, and an optional primary GitHub repository.
- Gantt view
A timeline view on the Tasks page with a subject toggle for Tasks, Sprints, or Milestones. Click any bar to open the entity.
- GitHub repo pool
Workspace owners can add a pool of GitHub repositories via Firebase's GitHub provider. Each project then picks one as its primary binding.
- Member invitations and roles
Workspace owners invite teammates by email. Roles at the workspace level and at the project level (maintainer, contributor, viewer).
A full developer-facing changelog — every fix, every root cause, every file touched — is kept alongside the code. The entries above are the user-facing summary of it .