LimeOSLimeOS
FRENBG
Resources

Give this to your AI. It will know how to build onLimeOS.

Your AI tool already knows how to write HTML, JavaScript and business logic. What it does not know is the platform its code will run on. These documents are written to be pasted into your assistant: from there, it produces an application that starts on LimeOS the first time.

What you do not write

Your AI knows how to write the screen. It does not know who is allowed to see it.

An operating system does not ask you to write the printer driver. LimeOS does not ask you to write accounts, permissions or security: they are already there, and your application plugs into them.

UsersAccounts, groups, sign-in, single sign-on. You write no login page, no password handling, no directory.
PermissionsPer-resource permissions, checked by the server before your code runs. You declare who is allowed; you do not implement the check.
SecuritySessions, isolation between applications, access control. An authentication hole in your application is not possible: you are not the one writing it.
Compatibility between applicationsYour applications call each other. They share the same users, the same permissions, the same storage.
A global file management APITree, folders, upload, locking, metadata, per-node permissions — for all your applications, with no storage to choose or administer.
PDF renderingAn HTML template becomes a paginated PDF. Pure Python, no system library to install.

What is left to write isyour application. The rest is provided — and it is precisely what your AI would not have got right.

Get started

Your first application in five commands.

These commands are for your assistant to type: give it the reference and it installs, publishes and checks on its own. A LimeOS application stays a plain HTML/JS application — the server serves your files and calls your code for the dynamic parts.

python vhtml.py new my-app --mount my-app --title "My application"
python vhtml.py install my-app# once: creates the application and its macros
python vhtml.py register my-app# once: claims the /my-app route
python vhtml.py push my-app# a macro changed
python vhtml.py res my-app# an html, a css, a js changed
Install once, then push.Never reinstall to change code: that is the rule that keeps what is already live from being lost.
The documentation

The seven documents to give your AI.

Paste them into your assistant: it finds there everything it could not have guessed. Every rule comes with the symptom that taught it, because those symptoms name the wrong cause almost every time — and an AI falls for it just like a human.

01Anatomywhat an application is made of, and which file becomes what
02Routinghow a URL reaches your code, and in what order
03Server codewhat your code sees: the request, the response, the libraries, the settings
04Front endthe page, its assets, and talking to your own endpoints
05Deploymentinstall once, push afterwards
06Debuggingwhere the errors are — most of them are silent
07Pitfallsthe table of traps, with what each one looks like
The seven documents and the command-line tool are downloaded from your management space as soon as you sign up — that is where your AI will find what it needs to know. The community itself is onlime-ai.org.
Reference

The HTTP/JSON API, in 43 actions.

Give this list to your AI: it will know what to call, and you will not have to explain it.

Session and identitylogin · logoff · change_root_password
Filescreate_folder · delete_node · update_node · upload_file · retrieve_tree · retrieve_folder_data
Storage, locking, metadataget_storage · list_storages · select_document · view_document · lock_document · unlock_document · submit_single_document · submit_multi_documents · list_metafields
Users and permissionsretrieve_node_rules · update_node_rules · retrieve_users · retrieve_groups
Applicationsget_plugin · install_plugin · call_macro
Synchronisation8 actions to synchronise between instances
Maintenanceupgrade · clear · selftest
The command-line tool, in 13 commands
newbuildinstalluninstallregisterpushrescheckverifylogsstacksmacroskv

Two that save time:verifywalks every route and names the dead ones;logsshows your application's log — the one that never appears in the server log, and that takes a while to find the first time.

Document templates

Five templates, from the plainest to the most prescriptive: the author imposes nothing, then the author takes the page over. Letter, invoice, quote, inspection report, and a probe that shows where the engine gives up.

Release notes

Three milestones published so far, each with what changed, written in plain words.

Deploy your first application today.

Talk to an expert
LimeOSLimeOSLimeOS is the operating system for applications built with AI.