web-edit
A Python web editing application developed by Simon Willison and published on PyPI, used to demonstrate performance profiling and visualization.
Timeline (last 90 days)
Simon Willison released web-edit 0.1a1, and this version includes performance optimizations.
The performance optimization code in web-edit 0.1a1 was written by Claude Opus 5.5.
According to the information in PR #1, Claude Opus 5.5's optimization work was submitted in the form of a pull request.
web-edit is still at an early stage, and 0.1a1 means the first iteration on the alpha channel.
Simon Willison used the Python 3.15 sampling profiler to profile his web-edit application, and with the help of GPT-6 Astra Extra High in Codex generated a flame graph and source heatmap through an AI coding assistant.
Simon Willison released a tool called web-edit 0.1a0, a small tool that provides a Web UI within a folder for browsing, uploading, and editing files.
Keeping sensitive data outside the agent's view, replacing permission systems with network isolation, and translating mobile-first into concrete technical choices are three takeaways that can be learned from web-edit.
Simon Willison's motivation for developing web-edit was that when developing with an AI coding agent on his phone, he needed to edit credential files but did not want the credential contents to enter the LLM context.
web-edit is designed to run inside a Tailscale network, so after the agent starts the service, users edit files directly from their phones via Tailscale, and credentials never pass through the model.
web-edit's file list page has a top-level title of WORKSPACE, contains three buttons—Refresh, Upload files, and New file—and its table lists Name/Size/Modified, with support for Download and Delete.
1 more timeline events
All Facts (11)
web-edit is still at an early stage, and 0.1a1 means the first iteration on the alpha channel.
50%UnverifiedThe performance optimization code in web-edit 0.1a1 was written by Claude Opus 5.5.
50%Unverifiedweb-edit is designed to run inside a Tailscale network, so after the agent starts the service, users edit files directly from their phones via Tailscale, and credentials never pass through the model.
50%Unverifiedweb-edit's file list page has a top-level title of WORKSPACE, contains three buttons—Refresh, Upload files, and New file—and its table lists Name/Size/Modified, with support for Download and Delete.
50%Unverifiedweb-edit displays images smaller than 2 MB inline, and selecting a text file enters editing.
50%UnverifiedKeeping sensitive data outside the agent's view, replacing permission systems with network isolation, and translating mobile-first into concrete technical choices are three takeaways that can be learned from web-edit.
50%UnverifiedSimon Willison's motivation for developing web-edit was that when developing with an AI coding agent on his phone, he needed to edit credential files but did not want the credential contents to enter the LLM context.
50%UnverifiedSimon Willison released web-edit 0.1a1, and this version includes performance optimizations.
50%UnverifiedAccording to the information in PR #1, Claude Opus 5.5's optimization work was submitted in the form of a pull request.
50%UnverifiedSimon Willison used the Python 3.15 sampling profiler to profile his web-edit application, and with the help of GPT-6 Astra Extra High in Codex generated a flame graph and source heatmap through an AI coding assistant.
50%UnverifiedSimon Willison released a tool called web-edit 0.1a0, a small tool that provides a Web UI within a folder for browsing, uploading, and editing files.
50%