>_

autoenv

agent-ready non-interactive

Directory-based environments.

How to install autoenv

npm install -g '@hyperupcall/autoenv'

autoenv use case

Automatically configure environment variables and trigger scripts when navigating between project directories.

When to use autoenv

  • Managing project-specific environment variables without manual export
  • Automatically activating or deactivating Python virtual environments upon entry/exit
  • Setting up local development paths or secrets required for specific repositories

When not to use autoenv

  • In highly security-sensitive environments where executing untrusted code on 'cd' is a risk
  • For global configuration that should persist across all shell sessions regardless of directory

autoenv features

  • · Automatic execution of .env files on directory entry
  • · Cleanup execution of .env.leave files on directory exit
  • · Nested environment support with directory tree walking
  • · Zsh and Bash compatibility

Want your agent to find this automatically?

Add the MCP server to your agent config and it will discover tools like autoenv on its own.

Set up MCP →

Similar tools to autoenv