Changelog

Marks

analyticscli

Marks are timeline annotations — a deploy, an incident, a release — pinned to your analytics so you can see what happened when a metric moved. Create them manually, from CI/CD, or automatically from plugins.

  • Manual — tell mark "Shipped v2.0" --category release from the CLI, or via the API
  • Automated — your CI/CD pipeline creates a mark on every deploy, with a link back to the commit
  • Plugin-emitted — plugins auto-annotate your timeline. When the GitHub plugin detects a release, or Cloudflare sees a traffic anomaly, a mark appears automatically

Categories

Marks carry a category that signals what kind of event it was:

  • Release — version deployments, feature launches, config changes
  • Incident — outages, degradation, error spikes
  • News — press coverage, announcements, external events that affect your metrics

Filter by category to see only what matters — tell mark list --last 30d --category incident shows recent incidents.

Private and public

Marks default to public (visible to workspace members). Mark something private and only you see it — useful for personal hypotheses, draft annotations, or notes you're not ready to share.

AI assistant

Your AI assistant can create and query marks. Ask it to annotate a deploy, list recent incidents, or find what changed around a date range.

New: Interactive explorer

Explore your data with tell -i. Six views in a terminal-based interface:

  • Status — live throughput and connection stats
  • Query — direct SQL access to your analytics
  • Tail — live stream of incoming data
  • Boards — browse and view dashboards
  • Ask — natural language queries powered by AI

Also in this update

  • Sign in with Tell — OAuth for team authentication
  • tell update checks for newer versions
  • Per-workspace throughput visible in tell status