You write with Claude Code, Cursor, Cline, whatever gets the job done. Copyrightable rides along and makes every AI-assisted commit carry authorship evidence you can hand to a client, a court, or a compliance review. Set it up once. Everything after that is on the record.
Three ways to wire it in
No new editor. No new workflow. One change in the tool you already use, and from then on the work you do lands in your evidence ledger.
One command installs a hook. Every prompt, file edit, and model response is hashed and recorded as you work, with zero change to how you code.
npx @interactivetech/copyrightable installWorks with Claude Code today
Paste our hosted connector into the connector settings, log in once, and register the sessions you want evidenced. Nothing to install or run on your machine.
https://mcp.copyrightable.app/mcpHosted connector, log in and go
Already did the work in a chat tool? Paste the conversation transcript and we build the evidence from the session you already had. No setup at all.
app.copyrightable.app/tryThe retroactive path, zero install
What you get
Captures roll up into a filing, a story, a file, or a whole repo, with a tamper-evident chain underneath it. Here is what shows up on your side.
See how much you authored versus the model, file by file and commit by commit, scored from the captures themselves.
Each record is hashed the moment it happens and linked to the last, so the timeline cannot be reordered or backdated after the fact.
Resolve the captures to a single Merkle root and certify it. You hold a portable record of who authored what, and when.
Every filing, session, and decision in one place, ready to export when a client, auditor, or court asks who wrote this.
Why a developer cares
The line between what you wrote and what the model wrote is now a real question, for your own IP and for everyone you ship to.
When a client claims the deliverable was machine-made, or a contractor claims the work as theirs, you answer with a dated authorship trail, not a memory.
License questions increasingly hinge on who actually authored a contribution. Your commits carry that provenance from the moment they land.
The US Copyright Office requires human authorship, and purely AI-generated code cannot be registered. Copyrightable documents the architecture, edits, and direction that were yours, so you can describe them when you file.
Security and legal teams are starting to ask for AI provenance on shipped code. You already have the record, hashed and timestamped.
Install the hook, add the hosted connector, or paste a transcript, and every AI-assisted change you ship from now on carries a dated record of the human decisions behind it.