Libraries

Scripts run inside your container with a standard set of libraries already installed: spreadsheets, Word documents, PDF, tables, and a document converter. Those cover most of what a back office process needs.

Asking for one more

When a job needs a library that is not there, the agent asks for it rather than installing it quietly. An agent cannot add a dependency during a run, because a library installed on the fly disappears on the next restart and takes the job with it.

What is checked before it is installed

The package is looked up and pinned to an exact version. Known vulnerabilities are checked and a critical one refuses the request. Everything the package would bring with it is checked as well, not only the package itself. A name that collides with something the platform uses is refused.

Who decides

A request that passes every check can install itself and you get a report. Anything with a finding becomes a real question with an Approve and a Reject, in the inbox, with the finding in front of the person deciding.

What you see

The list of libraries in your workspace, who asked for each one, when it was added and why. Total size is capped per workspace, so a container cannot grow without anyone noticing.