This repository was archived by the owner on May 29, 2026. It is now read-only.
[Exploration] docs: auto-activation concept page and cross-links#456
Draft
djsauble wants to merge 24 commits into
Draft
[Exploration] docs: auto-activation concept page and cross-links#456djsauble wants to merge 24 commits into
djsauble wants to merge 24 commits into
Conversation
Add documentation for the auto-activation feature (flox/flox#4117): - New concept page explaining auto-activation lifecycle, trust model, nested environments, deactivation, and hook state variables - Add note admonition and section in activation concept page - Add note admonition in default environment tutorial - Add auto-activation to mkdocs nav Man pages for `flox allow`, `flox revoke`, and `flox deactivate` will be generated from CLI source once the feature ships. Edits to the `flox activate` and `flox` man pages must happen in flox/flox. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
github-actions
Bot
added
the
documentation
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add a "Comparison with manual activation" section with a table covering trigger, activation mode, services, trust, deactivation, multiple environments, hook.on-activate, and error handling differences. Clarify that auto-activation starts all manifest services automatically (unlike flox activate which requires --start-services). Add admonitions for activation mode limitation and hook.on-activate subprocess isolation behavior. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Correct three inaccuracies identified during code review: - Hook installation applies to all eval-mode invocations, not just bare `flox activate` - Subshell exclusion applies to all subshell activations, not just `-d`/`-r` - Default environment section now explains the old `-r` pattern still works and gets auto-activation for free, and clarifies `eval "$(flox activate)"` doesn't fetch from FloxHub Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
djsauble
changed the title
mkenigs
reviewed
Mar 27, 2026
mkenigs
reviewed
Mar 27, 2026
mkenigs
reviewed
Mar 27, 2026
mkenigs
reviewed
Mar 27, 2026
mkenigs
reviewed
Mar 27, 2026
mkenigs
reviewed
Mar 27, 2026
mkenigs
reviewed
Mar 27, 2026
djsauble
commented
Mar 28, 2026
djsauble
commented
Mar 28, 2026
djsauble
commented
Mar 28, 2026
djsauble
commented
Mar 31, 2026
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
- Document 3-command model: eval "$(flox activate)", flox activate, eval "$(flox hook)" - Update trust model to latest-decision-wins (timestamp-based) - Update services to use manifest config option instead of auto-start - Unify deactivation around flox deactivate, clarify innermost-only constraint - Remove hook.on-activate isolated subprocess note (profile scripts run consistently) - Update comparison table (add Deactivation row, remove hook.on-activate/Services rows) - Add "Why auto-activation instead of direnv?" section to activation.md Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
djsauble
commented
Mar 31, 2026
djsauble
commented
Mar 31, 2026
djsauble
commented
Mar 31, 2026
djsauble
commented
Mar 31, 2026
djsauble
commented
Mar 31, 2026
djsauble
commented
Apr 2, 2026
djsauble
commented
Apr 2, 2026
djsauble
commented
Apr 2, 2026
djsauble
commented
Apr 2, 2026
mkenigs
reviewed
Apr 2, 2026
mkenigs
reviewed
Apr 2, 2026
mkenigs
reviewed
Apr 2, 2026
mkenigs
reviewed
Apr 2, 2026
mkenigs
reviewed
Apr 2, 2026
mkenigs
reviewed
Apr 2, 2026
mkenigs
reviewed
Apr 2, 2026
mkenigs
reviewed
Apr 2, 2026
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
Co-authored-by: Matthew Kenigsberg <matthew@floxdev.com>
- Rename flox enable/disable to flox allow/deny (mirrors direnv) - Remove hallucinated trust/security content; simplify to single eligibility check (whether auto-activation is allowed) - Cut "always" from auto_activate config; default to "never" - Use flox activate -D for default environment examples - Move command descriptions above comparison table; use in-place/subshell terminology - Remove redundant "Relationship to default environment" section - Add auto-activation preference storage path - Note that "never" config disables hook installation Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
djsauble
commented
Apr 3, 2026
djsauble
commented
Apr 3, 2026
djsauble
commented
Apr 3, 2026
djsauble
commented
Apr 3, 2026
djsauble
commented
Apr 3, 2026
djsauble
commented
Apr 3, 2026
djsauble
commented
Apr 3, 2026
djsauble
commented
Apr 3, 2026
Co-authored-by: Daniel Sauble <daniel@flox.dev>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds documentation for the direnv support project (https://linear.app/floxdotdev/project/direnv-support-328f1799fe33):
docs/concepts/auto-activation.md) covering:flox activate) and without (flox hook), plus a 3-command comparison tableflox allow/flox denycommands, interactive prompt for unregistered environments, single preference record per envauto_activateconfig option ("prompt"/"never") supporting phased rolloutDo not merge
This PR should not be merged until we've implemented the auto-activation feature. There's a prototype at flox/flox#4117 but the goal isn't to merge this directly.