Changelog

1. July 31, 2026

   Carlton retired

   Carlton is retired and no longer available in Jalapeño. We removed the chat surface, write mode, and assistant settings so the product can stay focused on the meeting-to-action workflow.

   The human review queue remains the control point for AI-extracted work. Suggested actions can be edited, confirmed, or dismissed, and nothing syncs or notifies an assignee until a person confirms it.

   • Retired the Carlton assistant and its write mode
   • Kept human review and confirmation as the boundary before sync
   • Removed assistant controls from the product and current documentation
2. June 12, 2026

   Calendar auto-join, action review, and a security hardening pass

   The feature this product was always supposed to have is now live: calendar auto-join. Connect Google Calendar or Outlook, switch on calendar sync and auto-join, and Jalapeño watches your calendar for meetings with Zoom, Google Meet, or Microsoft Teams links, then dispatches the notetaker bot automatically. The poller runs every few minutes, you can toggle the bot off for any individual meeting, and in-person meetings still record straight from the app.

   Extraction got a trust upgrade too. AI-extracted action items now land as suggestions instead of committed tasks. You review, edit, confirm, or dismiss each one, and nothing syncs to Linear, Jira, or Asana (and nobody gets notified) until you confirm it. Re-running extraction never destroys confirmed items, and duplicates are detected across meetings.

   Staying on top of the work got easier as well: in-app reminders for due-today and overdue items, consolidated overdue nudges in Slack capped at once a day, and a daily summary digest to your configured channel, all controlled by notification preferences that live server-side.

   Under the hood, a substantial hardening pass shipped. Linear and Jira webhooks are verified with HMAC-SHA256 and Recall.ai webhooks with Svix signatures including replay protection; in production, unverified requests are rejected. Changing or resetting a password now invalidates every other session, and a proper forgot-password flow exists. On reliability: hour-plus meetings are now processed in full through chunked extraction (the old transcript cutoff is gone), and a failed upload keeps your recording safe in the tab with retry and a download fallback.

   • Calendar auto-join for Zoom, Meet, and Teams meetings on Google Calendar or Outlook, with per-meeting opt-out
   • Action items arrive as suggestions; sync and assignee notifications fire only on confirm
   • Due-today and overdue reminders in-app, consolidated nudges and daily digests in Slack
   • Webhook signature verification, session invalidation on password change, and password reset
   • Full-transcript processing for hour-plus meetings and safer upload retries
3. May 12, 2026

   Real-time meeting processing stream

   Until this week, the path from 'meeting ended' to 'action items ready' looked like waiting for an email. That worked, but it left users staring at a stale meeting card for three to five minutes, wondering if anything was actually happening. We replaced it with a live, server-sent-events stream that drives the meeting page directly while transcription and extraction run.

   You now see the processing pipeline unfold in real time. Audio uploads, transcription progress, speaker diarization passes, and action item extraction each emit progress events. The meeting page subscribes via SSE, so progress and the AI summary stream in live, transcript sections land as each chunk completes, and action items appear when extraction finishes. Once everything is complete, the page transitions into a polished completed view with one fewer reload required.

   On the front end, every progressive state has its own loading skeleton. No more single 'processing…' spinner sitting on the screen for minutes at a time.

   • Live SSE feed for transcription and extraction progress
   • Polished completed-meeting view with transcript, summary, and action list inline
   • Single reload after pipeline completion, instead of polling
4. May 10, 2026

   Long recording reliability

   Multi-hour calls were occasionally getting stuck partway through processing. We dug in and found two distinct failure modes: FFmpeg chunking edge cases on certain audio codecs, and a transcoding step that silently dropped chunks past a duration threshold. Both are now fixed.

   The FFmpeg chunking pipeline has been hardened with explicit codec detection and conservative segment sizing. We also added retry-with-backoff for transcription chunks that come back with transient errors, so a single flaky chunk no longer fails the whole meeting. Multi-hour board meetings, all-day workshops, and full-day customer interviews now process consistently.

   On the UI side, when ingest does fail we surface the real underlying error message instead of a generic banner. Users get an actionable reason and a retry button rather than a dead-end.

   • Hardened FFmpeg chunking for long and unusual audio formats
   • Per-chunk retry with exponential backoff for transient transcription errors
   • Real error messages surfaced in the UI when ingest fails
5. May 6, 2026

   Full-width meetings UI refresh

   The meeting detail page has been redesigned end to end. Previously the layout was capped at a centered column that wasted real estate on wider monitors and made long transcripts feel cramped. The new layout is full-width with intentional content max-widths inside each panel, so transcripts breathe and side-by-side panels (summary, transcript, actions) line up cleanly.

   The in-meeting card at the top is new. It pulls together the speaker list, meeting duration, source platform, and quick links to the recording in one place, so you stop hunting around for basic metadata. The page header also sticks while you scroll the transcript, so you can always reach the action items tab and the share button.

   Readability on long transcripts improved meaningfully: tighter typography, better speaker-grouping, and a sidebar that lets you jump to specific timestamps without scrolling for thirty seconds.

   • Full-width meeting layout with intentional inner max-widths
   • New in-meeting summary card with quick metadata
   • Sticky meeting header for long transcripts
6. April 28, 2026

   Persistent recordings on Azure Blob Storage

   Recordings now live in Azure Blob Storage instead of ephemeral container disk. That sounds small, but the practical effect is large: recordings survive container redeploys, which means you no longer have a window during a routine deploy where a freshly captured meeting might be lost.

   Blob storage gives us server-side encryption at rest by default with Microsoft-managed keys, which is the foundation we needed to start building real retention policies. Customer-controlled retention is the next item on the storage roadmap.

   For day-to-day users, nothing changes in the UI. The change is behind the scenes, but it shifts Jalapeño from 'hope nothing crashes during a recording' to 'recordings are durable from the second they hit our infrastructure.'

   • Recordings persisted to Azure Blob Storage immediately on upload
   • Server-side encryption at rest with Microsoft-managed keys
   • Foundation for upcoming customer-controlled retention policies
7. April 20, 2026

   Carlton AI write capabilities (retired)

   Historical release note for the retired Carlton assistant: at the time, it could read workspace data and, with write capabilities enabled, create meetings, update tasks, and invite team members.

   The retired Carlton write mode was off by default per user. Each write action used a strict function call with explicit scopes and server-side permission checks.

   This retired feature required explicit confirmation before destructive operations. It is preserved here only as product history and is no longer available.

   • Per-user opt-in write toggle, off by default
   • Function calling with strict, permission-checked scopes
   • Explicit confirmation required before destructive operations

Note: changelog entries are dated by publication, not by commit. We batch ship-summaries every few weeks.