On 21 October 2026, SAGA became STORY and moved from private beta to public beta. This page lists what changed, what you need to do, and what STORY can and can't do yet. For the story behind the release, read What's New: SAGA is now STORY, and it's in public beta.
Action required by 4 November 2026: chats and schedules created before 28 September 2026 are no longer supported and will be deleted on 4 November, along with their history. Copy any brief you still need into a new chat, recreate its schedule and pause the old one.
What changed
Area | What changed | What it means for you |
Name | SAGA is now STORY | Same agent, same searches. Look for STORY on your launchpad. |
Report windows | Each schedule stores its window as a rule, and the system calculates the exact dates at every run, including time zones and clock changes | Briefings always cover the right period, with the right dates and weekdays |
Recipients | Saved with the schedule and used exactly as given | Briefings only go to the people you named |
Plans | A confirmed plan is required before scheduling, and it's carried into every turn and every run | Long chats and scheduled runs stay on the question you asked |
Scheduled runs | Run on Pulsar's servers, independently of your login | Logging out no longer stops a schedule |
Stuck chats | Fixed the issue that could leave a chat stuck at the planning step | Chats move from plan to report without getting stuck |
Working memory | Much larger context for each session | Typical analyses keep their full context from start to finish |
Search and filters | Search resolved once; country, source and hour-by-hour filters applied exactly | No repeated lookups and no filters loosened along the way |
Quotes | Quotes are the exact text of posts in your results, credited to the account that posted them | Every quote can be checked, including replies, quote posts and reposts |
Permissions | STORY runs with your Pulsar permissions, across every department in your team | You see your private searches and folders, and nothing beyond them |
Composer | Quick filters for search, date range and reply language | Set scope in a click, in plain language or both |
Reports | Open with a verdict, a 0–100 strength score and the change against the previous period; up to four charts | The headline and its evidence are in the first lines |
Chat list | Subject-based titles, a badge on scheduled chats, and several chats running at once | Easier to find and manage your work |
Moving an older chat to STORY
Open the older chat and copy your first prompt and any refinements. Save any reports you want to keep.
Start a new chat, paste in the brief, set the filters and confirm the plan.
Recreate any schedule and add your recipients.
Pause the old schedule so nobody receives duplicates, then work only in the new chat.
Chats can't be migrated automatically. If something goes wrong in an older chat, start a new one before reporting it: most issues in older chats are already fixed in STORY.
Current limits in the Public Beta
Schedules run at most once a day, with one schedule per chat.
Each chat works within one Pulsar domain. Cross-domain analysis isn't supported.
Reports support nine chart types, and unsupported types fall back to the closest one.
Pattern classification needs at least 30 days of data. Lifespan and volatility are unreliable for windows under 7 days.
Virality forecasts describe likely trajectories. They aren't guarantees.
Email briefings use basic formatting for now.
Coming next
A faster, more efficient analysis engine
An in-app meter showing how much of your usage allowance remains
Better-formatted email briefings
More frequent schedules