Set up the file editor
The editor plugin adds a browser workbench for Project files: a code editor, previews, file management, uploads and read-only Git history. The user side is Open, look at and save a file.
Install the plugin
- Open Settings → Available plugins and install editor.
- Check the registry for the plugin's current version and the minimum Chetty version it needs.
Disabling the plugin removes its UI and makes its file API unavailable, while Project registration and task Git history keep working.
Project and System roots
A Project has a Project root with the Project's own folder. In a managed Project there is also a System root with that environment's whole filesystem, including persistent directories such as /opt; anyone who can open the Project can browse it, not only administrators.
Git history belongs to Project. Administrators also get a System root for the host's persisted filesystem. Kernel virtual filesystems are excluded from it.
On a paired computer, Project opens the directory where the Chetty connection runs and System opens that computer's filesystem root, which on Windows is the drive or share containing that directory. Git status and commit history come from that computer's own checkout.
Editor limits
- Editable text is limited to 2 MiB. Image, PDF and media previews support files up to 50 MiB; Office previews support 20 MiB and generated PDFs 50 MiB.
- At most two Office previews convert at once; a request made while two are running is refused.
- Downloads are streamed, and uploads are offered only under the Project root, not under System. Chetty's own transport limits, declared-size checks and available storage still apply.
- Both roots list one directory level per request.
Developer reference
Implementation and browser contracts describe command execution, JSON writes and the browser lifecycle.