Project history
Typillar keeps a full record of every project: the tickets you asked for, the builds that ran, the code that was committed, and the deployments that went live. This record isn’t a side effect — it’s part of how the system works.
What’s recorded
Section titled “What’s recorded”The project’s event log carries one entry per thing that actually happened:
| Event | When |
|---|---|
| Ticket created | you asked for something. |
| Build started / succeeded / failed | the agent ran on a ticket. |
| Build paused | a platform restart interrupted a build in progress. |
| Deployed | you shipped, and the project went live at a URL. |
| Rolled back | a live deployment was taken offline. |
| Backup dropped | a build succeeded, but committing it to GitHub failed. |
Alongside it: the commits, in your GitHub repository, and the decisions each ticket accumulated as it was built.
Together these give you an unbroken chain from “I typed a sentence” to “this is what’s running.”
Where to find it in the console
Section titled “Where to find it in the console”The record sits in two places, because it answers two different questions.
Build tab → History. What happened, in order: tickets created, builds run and how they ended, deploys, rollbacks. The same pane lists your app’s versions, and each one has a Restore button — this is where you go back to earlier code. Next to it, the Code pane shows the app as it stands right now, read-only.
Overview → Deployments. What is actually running in your Cloudflare account: each resource the project provisioned, and, on a live Worker, a Roll back button that takes that resource offline while leaving the script in place. Roll back is per-resource — there is no single project-wide switch.
The split follows the two ways to undo: Restore changes the code, Roll back changes what the public can reach. See Deploys & rollback.
Why the history matters
Section titled “Why the history matters”For you. You can trace exactly how the project reached its current state — useful when reviewing what an agent did, onboarding a collaborator, or just remembering why something exists.
For restore. Returning to a known-good version is only trustworthy because the history is complete.
For the agents. The agents read the history — and each ticket’s decisions — to understand what already exists, so each new build fits the project instead of repeating or contradicting it. See Agents & the control plane.
Where the history lives
Section titled “Where the history lives”The code half of the history lives in your GitHub repository — fully yours, readable with ordinary Git tools, and intact whether or not you keep using Typillar. The console ties that together with the tickets, the builds, and the deployments, so you can see the whole story without leaving the project.
Related
Section titled “Related”- What you own — why the record is portable.
- Connect GitHub — where the commits land.