Self-improving AI Employees for everyone
Python ai-agentsai-employeeai-employeesassistantautonomous-agentsco-employeescompanygrok-botinstinctloop-agentsmuseown-your-datapersonalself-hosted
fix(npm): ship pyproject.toml + strip VIRTUAL_ENV in postinstall
trohitg800003670def
diff --git a/package.json b/package.jsonindex 47080f2c..ed2245fd 100644--- a/package.json+++ b/package.json@@ -53,6 +53,7 @@"!**/node_modules/","!**/.vite/",".env.template",+ "pyproject.toml","README.md","install.sh","install.ps1"diff --git a/scripts/install.js b/scripts/install.jsindex 37890e3e..e3f10b0d 100755--- a/scripts/install.js+++ b/scripts/install.js@@ -23,12 +23,20 @@ const ROOT = resolve(__dirname, '..');process.env.PYTHONUTF8 = '1';function run(cmd, cwd = ROOT, timeoutMs = 300000) {+ // Strip VIRTUAL_ENV from the spawned env. When the user runs+ // ``npm install -g machinaos`` from a shell that has activated a+ // venv (very common during dev), uv emits a noisy ``VIRTUAL_ENV+ // ... does not match the project environment path`` warning per+ // invocation. uv only honours VIRTUAL_ENV with ``--active``, which+ // we never pass, so dropping it at the source is the documented+ // workaround. Same fix applied to cli/supervisor.py's _full_env.+ const { VIRTUAL_ENV, ...cleanEnv } = process.env;execSync(cmd, {cwd,stdio: 'inherit',shell: true,timeout: timeoutMs,- env: { ...process.env, MACHINAOS_INSTALLING: 'true' }+ env: { ...cleanEnv, MACHINAOS_INSTALLING: 'true' }});}