hyperupcall/autoenv

Directory-based environments.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 53 minutes ago
Type:CLI ToolCategory(s):Terminal, Shell & TUIDeveloper Tools
Added to GitGenius on September 11th, 2026
Created on February 12th, 2012
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 271
Total Stargazers: 6,051 (+0)
Total Subscribers: 70 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.7 days
Mean response time: 160.0 days
90th percentile: 467.9 days
Tracked items: 19

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 10
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 634 days
Stale 30+ days: 9
Stale 90+ days: 9

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type/bug (11)
  • type/feature (6)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Autoenv is a shell extension that automatically executes environment setup files when you change directories.

The tool solves the problem of managing per-project shell environments by watching directory changes and executing `.env` files automatically when you enter a directory. When you `cd` into a directory containing an `.env` file, autoenv sources it, applying project-specific environment variables, virtual environment activations, or other setup commands. The tool also supports `.env.leave` files that execute when leaving a directory, allowing cleanup operations. Autoenv walks up the directory tree to the mount point and executes all `.env` files in order, enabling nested environment configurations.

This approach suits developers working with multiple projects that require different environment configurations, such as Python virtual environments, language-specific tools, or project-specific variables. It eliminates the need to manually activate environments or remember to run setup scripts when switching between projects. The tool works with both Bash and Zsh shells and can be installed via Homebrew, npm, or by cloning the repository directly.

The project maintains active continuous integration testing across its codebase. Development activity shows consistent attention to code quality and reliability through automated testing workflows. The tool receives ongoing maintenance with responsiveness to issues and pull requests, indicating sustained engagement with the user base.