Integrations
Planned to work where your notes already live.
Timbercut is designed to read feedback in the tools your team already uses and to make changes in the tools your editors use. These connections are planned, not live. This page says what each one is meant to do and what runs today.
- On this site
The interactive demo: a scripted simulation of one revision round on sample data, with a real audit download.
- In development
The Timbercut revision agent itself.
- Planned
All 7 tool connections on this page. None is live, and none is a partnership.
Planned connections
Seven tools, two jobs.
Notes come in from review, chat, docs and storage. Changes go out to editing and motion tools. Which ones come first will follow what pilot teams actually use.
Understand
Where notes arrive
Read feedback where people leave it, and send each question back to the person who can answer it.
-
Planned
Frame.io
Review and approval
- Planned to read
- Timecoded comments, replies, approvals and version stacks on review links.
- Planned to do
- Post the round’s outcome back as replies, and add the next version for review.
-
Planned
Slack
Team chat
- Planned to read
- Notes left in project channels and threads, with who said what and when.
- Planned to do
- Send each approval request to the person who owns it, in the thread it came from.
-
Planned
Notion
Docs and notes
- Planned to read
- Notes docs, briefs, call recaps and decision logs.
- Planned to do
- Write the round summary and open questions to a page you choose.
-
Planned
Google Drive
Files and storage
- Planned to read
- Briefs, brand kits, delivery specs and the asset versions they point to.
- Planned to do
- Flag files that are missing or out of date, and list where it looked.
Execute
Where changes are made
Apply supported changes in the tools editors already use, always as a new version.
-
Planned
Adobe Premiere Pro
Editing
- Planned to read
- Sequences, clips, markers, captions and the media each clip uses.
- Planned to do
- Apply supported operations such as trims, swaps, reorders and text changes to a new sequence.
-
Planned
DaVinci Resolve
Editing and color
- Planned to read
- Timelines, clips, grades and the media pool.
- Planned to do
- Apply supported timeline operations and grade matches to a new timeline.
-
Planned
Adobe After Effects
Motion graphics
- Planned to read
- Compositions, text layers and template controls.
- Planned to do
- Update text, lockups and end cards in templates, then render the changed comps for review.
Product names are trademarks of their respective owners and are used only to describe planned compatibility. Listing a tool here doesn’t mean a partnership, endorsement or working integration. There are no “connect” buttons on this site because there’s nothing to connect yet.
Ground rules
How every connection is meant to behave.
Production tools hold work that took weeks. These rules apply to every connector, whatever tool it talks to.
- 01
Access one project at a time
Each connection is designed to ask for access to a specific project, not a whole workspace, and to show you exactly what it can see.
- 02
Read before writing
Notes, files and history are read first. A missing file is reported with the places that were searched. It’s never guessed.
- 03
New versions only
Changes go into a new sequence, timeline, comp or page. The previous version stays exactly as it was.
- 04
People approve in their own tools
Anything subjective, costly or against a rule waits for a named person, asked where they already work.
- 05
Everything on the record
Every read, change and decision is written to the round’s audit and the Creative Decision Graph.
Architecture
How the pieces are designed to fit.
Claude is the intended reasoning and orchestration layer. It works over the project context and reaches production tools through connectors. A person approves what matters and signs off the round.
01Sources
- Review links
- Chat threads
- Notes docs
- Call notes
- File storage
02Project context
- Brief
- Brand, legal and delivery rules
- Transcript and captions
- Representative frames
- Asset metadata
- Decision Graph
03Reasoning and orchestration
Claude
- Interprets each note against the context
- Writes explicit edit operations
- Chooses which tool to call, and when
- Stops and asks when a person should decide
04Tool layer
Connectors expose each tool’s actions as defined tools with scoped permissions, using the Model Context Protocol (MCP) where it fits.
- Editing
- Motion
- Review
- Chat
- Docs
- Storage
05Verify and sign off
- Checks against each request and rule
- Revision audit and Decision Graph update
- Approvals from named people
- A person signs off the round
Why Claude
A revision round is mostly reading: notes, briefs, rules, transcripts and history, and then deciding what each note means. Timbercut is designed around Claude, Anthropic’s AI model, for that reasoning and for planning which tools to use. Timbercut isn’t affiliated with or endorsed by Anthropic.
Why MCP, where it fits
The Model Context Protocol is an open standard for connecting AI applications to tools and data. Using it where a tool suits it keeps each connector separate, with its own permissions, and lets new tools be added without changing the core.
What this website runs
None of this architecture. The demo is a scripted simulation in your browser. Nothing on this site calls Claude or any other AI model, holds credentials or connects to a tool.
For technical evaluators
What runs where.
This website is static files: it needs no server, database or credentials. The product will need a secure backend, and this is where it would connect.
| Part | On this website today | In the product (planned) |
|---|---|---|
| A revision round | A scripted simulation on fictional sample data, running in your browser. | Real notes, files and project data from the tools your team connects. |
| Reasoning | None. The first pass is scripted, and no AI model is called. | Claude, called from Timbercut’s servers, never from a browser. |
| Tool connections | None. | One connector per tool, with credentials stored and used on the server. |
| Edits | A simulated V8. Nothing is edited or rendered. | New versions in your editing and motion tools. |
| Audit | A real JSON or CSV download of the simulated round. | The same structure, for real rounds. |
| Your data | Stays in your browser. See the privacy page. | Stored and accessed as agreed in writing for each pilot. |
The only optional server this site can use is a form service for pilot enquiries, which the site owner can configure. Without one, the enquiry form prepares a message for you to copy, download or email, and sends nothing itself.
Tell us what your round runs on.
The pilot enquiry asks which tools your team uses, so the first connections follow real workflows.