| Filename | Latest commit message | Latest commit date |
|---|---|---|
This is a one-way door. agent-stories was source-available: paying customers got the source and the build pipeline. It is now a marketing project, measured by adoption, and adoption needs public source on GitHub. Code released under the AGPL stays available under it, so this cannot be undone for any version already published. AGPL-3.0-only, not a permissive license: anyone who ships or hosts a modified version must publish its source, so nobody can take the form factor closed. "Only" fixes the terms at version 3. The license covers the code, not the name or the logo, so a fork must also use a different name and icon. A later relicense stays possible only while I hold all copyright. README.md takes contributions as problem reports, not pull requests, so no outside code enters the repo. |
||
| .forgejo | ||
| apps | ||
| config | ||
| docs | ||
| lib | ||
| plan | ||
| scripts | ||
| self-hosting | ||
| .envrc | ||
| .gitignore | ||
| .plan | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| human-tasks.md | ||
| LICENSE | ||
| questions-while-away.md | ||
| README.md | ||
| rust-toolchain.toml | ||
Video reviews for coding agents. Stories for you and your team.
Watch what your agents build, add your face and narration, and share the result.
Setup · Features · How it works · Contributing · Documentation
Overview
Coding agents can produce changes faster than you can review and explain them. Reviewing that work still often means reading pull requests and asking the agent what changed. Showing it to customers or colleagues takes another round of recording, editing, and publishing.
At the same time, everyone is vibe coding. There is more software competing for attention, and a demo alone does little to help people remember who's behind it. Your customers and colleagues need to get to know you and the work you're responsible for shipping.
agent-stories brings review and presentation into one workflow. Its demo skill teaches your existing agents to explain the product impact of their changes in video, so you can see what they did without reading a wall of text or trying to decipher an awkward explanation.
Getting agents to make good explainer videos takes tedious testing and refinement. The skill gives developers a way to share that work. As people contribute improvements, everyone's agents get better at explaining what they built.
Watch the demos on your phone and reply with feedback. When the work is ready, record an explanation with your face overlaid on the demo, edit the video, and save it to share through your usual apps.
You can use it with your own agents or invite colleagues into a shared team. Agents belong to the team, including unattended bots that choose and ship work on their own. Anyone on the team can pick up a demo and present it. A feed of finished stories lets everyone keep up with what other engineers and their agents are shipping.
Setup
Install agent-stories for iPhone. Open Connect an agent in the team menu and follow the instructions to install the skill and pair your agent. For Claude Code, the app supplies the plugin commands and a pairing code.
Ask your agent to record and publish a demo, then open the story on your phone.
- Review the work. Watch the demo and reply with feedback if something needs to change. The reply goes back to the agent so it can make another pass.
- Record your explanation. If you're happy with the work, tap Ship. The demo plays while you record a voiceover with your face in a picture-in-picture overlay. Do as many takes as you want until you nail the explanation.
- Edit in the app. Position your face overlay, add captions or stickers, and preview the result. Keep adjusting it until you're happy with the video.
- Save and share. Save the finished video to your camera roll, then import it into Slack, Instagram, TikTok, Twitter, Teams, Telegram, WhatsApp, or whichever app you use to reach your audience.
To use it with colleagues, invite them into the same team and connect your team's agents. Finished stories posted to the team appear on everyone's phones.
Features
- A shared demo skill. Teach your existing agents to explain their work in clear videos, and benefit from improvements contributed by other developers. Watch the demos on your phone and send feedback back to the agent.
- Shared teams and agents. Connect personal or unattended agents to a team. Teammates can review their output and turn a demo into a finished story.
- Lightweight video editing. Record your face and narration over a demo, add stickers and TikTok-style burned-in captions, and arrange the video with simple editing tools.
- Camera-roll export. Save the finished video and publish through the social and messaging apps already on your phone, using your own accounts.
- Team story feed. Swipe through finished videos from teammates to keep up with what's shipping across the team.
- Usage and impact metrics. Export metrics on your team's adoption for your promo packet (for the big tech folks).
What you can do with it
- Teach your existing agents to make clear explainer videos that show the problem they solved and what the change means for the people using your product
- Pick up a demo from an unattended team agent and turn it into a product update
- Show a customer how you solved their problem, with your explanation alongside the working feature
- Publish regular demos that help customers and colleagues get to know you and the work you ship
- Keep up with other engineers' work through the team's finished stories
- Document team adoption in your promo packet with concrete metrics from the workflow you introduced
How it works
Your agent installs a skill plugin, records a demo, and uploads the video to an S3 bucket. The phone app reads the video from that bucket and presents it as a story. Replies go back to the agent that published the demo.
When you're ready to present the work, record yourself while the demo plays. The app combines your face, narration, stickers, and captions into a finished video on your phone. You can publish it to the team feed, save it to your camera roll, or both. Sharing outside the team happens through your own apps.
A team's screen has two places. Agent demos is where the bots' raw recordings land, as rings. Team stories is what the team shipped: the finished videos people recorded and posted, newest first, each credited to the demo it explains. Teammates swipe through them on their own phones; a manager can open the team and see what people are shipping without reading the agents' queue.
agent-stories is self-hostable on infrastructure your team already controls, including on your office Wi-Fi. Demos can stay within that infrastructure until you choose to share them. The recording and editing tools live in the work app, so making a video for Slack doesn't require opening Instagram at work.
Contributing
We take contributions as written problem reports, not pull requests. Open an issue describing what you were trying to do, what happened, and what you expected. Include steps to reproduce the problem when you can.
If a fork makes the bug easier to reproduce, include a link in your issue. We'll pull it, build it, and fix the problem.
License
agent-stories is free software under the GNU AGPL v3 only. The agent-stories name and logo are trademarks and are not covered by the license.
Going deeper
- Claude Code plugin — installation and connecting your agent
- CLI — uploading demos and reading replies from a terminal
- Product behavior — the rules for stories, narration, teams, and feedback
- Development guide — building and testing the project from source