From the source

How it works
- The procedure applies to Screen-slot footage, not the camera slot. It uses timeline, storyboard and individual-frame inspection.
- Blur regions use percentage coordinates, startTimeMs and durationMs. add_blur creates a region; update_blur adjusts it. Moving details may need multiple regions.
- Check the first and last visible moments and the finished export. Sampled frames can miss brief exposure, so a blur does not prove complete redaction.
- Recorded passwords or API keys still require rotation. Editors can remove blurs and earlier exports can retain secrets.
- The guide says MCP is included on every plan and the seven-day trial. The original prices remain Pro $13 and Premium $19 per user/month with annual billing. Agent costs and total workflow cost are not verified.
Workflow guide
Connect only the authorized Tella workspace through Model Context Protocol (MCP), the agent tool connection. Confirm the recording before using get_timeline to locate Screen-slot clips.
Use get_storyboard and get_video_frame to locate sensitive regions and their first and last visible moments, including movement between views.
Obtain explicit approval for blur edits before changing the recording.
Call add_blur with percentage-based position and dimensions, startTimeMs and durationMs. Use update_blur or multiple regions when details move.
Check boundary frames and the full local export. Rotate recorded passwords or API keys regardless of the blur before seeking human release approval.
Count missed regions and uncovered frames in the consented test recording. Block release if any known exposure remains.
Sources and downloads
Try Tella with Thomas’s referral link ↗ · We may receive a referral benefit.
Discuss this workflow →