On the machine
What the es-python installer leaves on your computer besides the runtime: the on-machine manual, the build records, the eyalsec helper command, and a context file for AI coding assistants.
The EyalSec home folder
Every es-python install creates ~/.eyalsec/ in your home directory. It holds documentation and records only; the runtime itself lives under ~/opt/ (see Where it is installed).
| Path | What it is |
|---|---|
~/.eyalsec/manual/ |
a short manual for es-python, readable offline |
~/.eyalsec/AGENTS.md |
a context file for AI coding assistants |
~/.eyalsec/builds/<name>.json |
one record per installed build |
Each runtime also has a small settings file at ~/opt/eyalsec…/etc/eyalsec.conf, which records the EyalSec address the machine reports to and the site-packages directories it shares with your regular Python. The installer writes it; you do not need to edit it.
The eyalsec helper command
The installer also puts a small eyalsec command in ~/.local/bin. It works with the files in ~/.eyalsec/ and never changes your machine's settings.
| Command | What it does |
|---|---|
eyalsec info |
list every es-python build installed for your user |
eyalsec manual |
show where the on-machine manual is and list its pages |
eyalsec agents-init |
make the AI assistant context available in the current project |
eyalsec help |
list these commands |
eyalsec info
eyalsec info prints one block per installed build, read from ~/.eyalsec/builds/. Each block shows the install folder name, the Python version, the launcher command (for example es-python3.13), where it is installed, the EyalSec server it reports to, the build string and when it was installed.
Use it to check which versions are on a computer, or which server a build talks to when you are troubleshooting.
eyalsec manual
eyalsec manual prints the manual's location and lists its pages. The pages are plain Markdown files; open them with any text viewer, for example less ~/.eyalsec/manual/10-using-es-python.md. This online guide covers the same ground in more detail.
AI coding assistants
~/.eyalsec/AGENTS.md explains es-python to an AI coding assistant (Claude Code, Cursor, Codex and similar): what es-python is, that it should run your code with it, and how packages work. With it loaded, the assistant does not "fix" a problem by switching back to plain python.
To load it into a project, run this in the project's top folder:
cd ~/src/my-project
eyalsec agents-init
What it does depends on what the project already has:
- If the project has an
AGENTS.mdorCLAUDE.mdfile, it adds one line,@/home/you/.eyalsec/AGENTS.md, to the end of it. Running it again does nothing. - Otherwise it creates
AGENTS.mdin the project as a link to~/.eyalsec/AGENTS.md, so it stays current when you reinstall.
es-python -h also prints these paths at the end of its help text.
Uninstalling
Uninstall from the dashboard, which gives you a one-line command to run on the computer; see Uninstall. The uninstall command removes:
- every es-python runtime under
~/opt/eyalsec*, including other Python versions installed for other machines on the same computer, - the
es-python*andeyalseccommands in~/.local/bin, - the whole
~/.eyalsec/folder, - the
PATHline the installer added to~/.bashrc,~/.zshrcor fish'sconf.d.
It does not touch your projects, your regular Python, or packages you installed into ~/.local with pip; those are shared with your regular Python and stay usable by it.
What is left behind
Anything eyalsec agents-init added to a project stays there after an uninstall. The AGENTS.md link becomes a broken link, and the @…/.eyalsec/AGENTS.md line in an existing file points at a file that no longer exists. Remove them by hand if you no longer want them.
Virtual environments you created with es-python also stop working, because the runtime they point to is gone. Recreate them with your regular Python.
After uninstalling, open a new terminal (or run hash -r) so your shell stops looking for es-python.