Skip to main content

Changelog

What this changelog is​

The ReelBot Changelog is a chronological record of:

  • new features
  • improvements
  • fixes
  • behavioral changes

It exists to document what actually changed, not to market releases.

If something behaves differently than before, it should appear here.


How to read this changelog​

Each entry follows a simple structure:

  • Added → new features or capabilities
  • Improved → enhancements to existing behavior
  • Fixed → bug fixes and reliability improvements
  • Changed → intentional behavioral or workflow changes

Not every release includes all categories.


Release cadence​

ReelBot ships continuously.

That means:

  • small updates may happen frequently
  • some changes ship silently unless behavior changes
  • documentation is updated alongside product changes when relevant

The changelog focuses on user-impacting changes.


What gets logged​

The changelog includes changes that affect:

  • creation workflows
  • generation behavior
  • captions, voice, or assets
  • publishing and channels
  • limits, usage, or plans
  • account, security, or billing behavior

Pure refactors or internal optimizations may not appear unless they affect outcomes.


What does NOT get logged​

The changelog does not include:

  • internal experiments
  • temporary feature flags
  • UI copy tweaks with no behavioral impact
  • infrastructure-only changes with no user effect

The goal is clarity — not noise.


Versioning approach​

ReelBot does not use traditional semantic versioning.

Instead:

  • changes are grouped by date
  • each entry reflects what went live
  • breaking or behavioral changes are called out explicitly

This matches how CreatorOps systems evolve in practice.


Recent updates​

December 2025​

Added​

  • Smart B-roll Suggestions
    • AI-assisted asset discovery in the Video Studio (Assets step)
    • Automatically suggests relevant stock videos based on topic, script, tone, language, and orientation
    • Curated results include short reasoning for each suggested clip
    • Smart search chips for quick manual exploration
    • Manual keyword search remains available at all times
    • Each successful request consumes 3 AI Credits
  • Speech Marks–based voice generation
    • Improved word-by-word caption accuracy
    • More precise highlight timing
  • Tone selection for topic & script generation
    • Professional, casual, humorous, inspirational, educational
  • Draft-safe regeneration system
    • Impacted Steps Warning prevents silent data loss
  • Publish drafts
    • Save posts without publishing
    • Publish later with validation
  • Brand Presets
    • Caption colors
    • Highlight colors
    • Logo placement and sizing

Improved​

  • Caption timing accuracy across all supported voices
  • Asset reuse across projects and drafts
  • Clearer usage indicators for AI credits and limits
  • Publishing validation before quota consumption
  • Asset cards now adapt dynamically to project orientation
    • Portrait (9:16), Square (1:1), Landscape (16:9)
  • Unified asset grid design across Smart Suggestions and Manual Search
  • Asset interaction overlays (Preview / Use) for clearer selection and feedback
  • Visual loading state when adding assets to a project

Fixed​

  • Edge cases where captions desynced after voice regeneration
  • Asset preview failures under slow networks
  • Incorrect blocking when limits were not actually exceeded
  • Draft loading now correctly restores content language
  • Manual search grid layout inconsistencies
  • Smart chip click handling for immediate search execution
  • Overlay pointer events causing unintended background clicks

How this changelog evolves​

This changelog:

  • grows over time
  • reflects real shipped behavior
  • stays aligned with documentation

If something feels undocumented, it probably belongs here.


The CreatorOps perspective​

In CreatorOps, systems don’t just change — they accumulate decisions.

The changelog is:

  • institutional memory
  • behavioral contract
  • trust mechanism

If it changed how you work, it should be logged.


Where to go next​

  • Features Overview → understand current capabilities
  • Troubleshooting → resolve unexpected behavior
  • Getting Started → onboard new users

This changelog is the record. The docs are the explanation.