TL;DR
Thorsten Meyer says he built the first working version of Docestra with an AI coding agent on Nov. 6, 2026, then spent six days addressing problems found in real PDF files and reviews. His project records report fixes for saving, encrypted files and redaction, while time and cost savings remain unmeasured and version 2.0 is still in development.
Meyer describes Docestra as a local TypeScript web app running in a browser on his Mac, with files kept on the machine. The first version could open and search PDFs, add annotations and signatures, fill forms, rearrange pages and save files. He says he gave the coding agent a one-sentence brief and committed that version at 21:47 Central European Time on Nov. 6. The project records identify Claude Code running Claude Opus as the code-writing agent and OpenAI’s Codex as a reviewer.
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
A robustness run over 930 real PDFs found that saving some files could produce a damaged cross-reference table, causing markups to disappear from the saved document. Meyer says he changed the save process to avoid compressed object streams. In a separate check, 52 of 69 encrypted PDFs disallowed annotations under their authors’ restrictions. Because the PDF library could not restore encryption after editing, Docestra was changed to require confirmation before unlocking those files and to save an unprotected copy without overwriting the original. The project log says all 69 test files then unlocked.
The editor’s original “white-out” feature only covered text; the underlying content remained in the PDF. Meyer says a first attempt at real redaction drew 14 problems in an independent review, followed by 13 in a second round. He abandoned that design for a simpler one. The project material reports no leaks in a test of 917 PDFs, but does not provide the test protocol or independent results. Version 1.5.1, dated Nov. 12, is listed with 745 unit tests and 32 browser test suites.
Why PDF edge cases matter
The project illustrates a practical difference between a feature demonstration and software used on everyday documents. A save defect can silently remove annotations, while a visual cover-up that leaves text underneath can expose information a user believes was removed. Testing varied files and reviewing the implementation surfaced risks that a small set of sample documents did not.
Meyer’s account also highlights that some decisions are product and safety choices, not just code fixes. For encrypted files, the editor’s inability to reapply protection led him to require confirmation and preserve the original. That approach makes the resulting copy’s status explicit, though users still need to handle it as an unprotected document.
The account is a developer’s report about a private tool, not an independent evaluation of AI coding or PDF editors generally. Meyer says he has not measured time or cost savings, so the project does not establish whether the approach is more efficient than other development methods.
Products Worth Considering
Samsung Galaxy Tab A11 8.7-Inch Wi-Fi Tablet, 64GB, 4GB RAM, 90Hz, Gray, with 20W Charger
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
Logitech MX Mechanical Wireless Illuminated Keyboard, Clicky Switches
As an affiliate, we earn on qualifying purchases.
Six days of Docestra revisions
The project timeline starts on Nov. 6, 2026, with the initial build and the 930-file robustness run. On Nov. 7, Meyer recorded the encrypted-file restrictions and chose to unlock only with confirmation, saving a separate unprotected copy. On Nov. 8, the redaction feature went through two review rounds before the design changed.
By Nov. 12, the project had reached version 1.5.1, which the supplied records list with 745 unit tests and 32 browser test suites. Meyer says work on version 2.0 began Nov. 13, with a planned shared PDF engine for AI agents. The source material calls that version a plan under development, not a finished feature.
Docestra is described as a private project that is not available for download. The chronology and test counts come from Meyer’s development log, plans and commit history; they have not been independently verified in the supplied material.
““Vibe coding gets you a working tool quickly. Turning it into a tool you can rely on is the real work.””
— Thorsten Meyer, describing the project’s conclusion
Testing claims and open questions
The supplied project records do not show how the 917-PDF redaction test was designed, which kinds of documents it covered or whether the results were independently reproduced. The reported zero leaks should therefore be read as a project test result, not proof that redaction is error-free in all documents.
It is also unclear how Docestra performs with PDFs outside the tested collections, whether later versions changed the encryption or redaction behavior, and when version 2.0 might be completed. The tool is private and unavailable for download, limiting outside assessment. No time or cost savings have been measured, according to Meyer.
Version 2.0 remains in development
Meyer says development of version 2.0 began on Nov. 13, 2026, with a shared PDF engine for the project’s AI agents as its planned direction. The source material gives no release date and says the work is unfinished. Further details about its implementation, testing and availability remain pending.
For people relying on an AI-built tool, Meyer’s project account points to a concrete next step: check how it handles the kinds of files used in practice, including saving, restrictions and sensitive content. The records do not provide a general certification or an independent audit of Docestra.
Key Questions
What is Docestra?
Docestra is a private PDF editor Meyer says he built with AI coding agents. It runs locally in a browser on his Mac and is not available to download.
What problem did testing find in saved PDFs?
A run over 930 PDFs found that saving some files could damage a cross-reference table and make markups disappear. Meyer says he changed the save process to avoid compressed object streams.
What did the encrypted PDF test show?
According to Meyer’s project records, 52 of 69 encrypted PDFs disallowed annotations under their authors’ restrictions. The editor was changed to require confirmation before unlocking and to save an unprotected copy without replacing the original.
Was the redaction feature independently proven safe?
The project material reports no leaks in a test of 917 PDFs after a redesign. It does not provide the test protocol or independent results, so the finding is a reported project result rather than a universal guarantee.
Is Docestra version 2.0 available?
No. Meyer says work began on version 2.0 on Nov. 13, 2026, with a shared PDF engine planned. The version was still in development, with no release date given.
Source: Thorsten Meyer AI
