docs: fix drift in Environment Variables - #272
Draft
jack-arturo wants to merge 1 commit into
Draft
Conversation
- PORT defaults to 8001 in AutoMem; drop the Flask-defaults-to-5000 myth - remove fabricated LOG_LEVEL and FLASK_ENV rows; neither is read - SEARCH_WEIGHT_RELEVANCE weights consolidation decay, not LLM scoring - JIT_ENRICHMENT_ENABLED runs inline on recall, not on store Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EiTAbgmncBDToAzqj71wka
Deploying automem-website with
|
| Latest commit: |
f3a919d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0a9e7b34.automem-website.pages.dev |
| Branch Preview URL: | https://docs-audit-getting-started-e.automem-website.pages.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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Automated docs-accuracy audit of
getting-started/environment-variables. Two rows documented variables the service never reads.PORT=8001is mandatory on Railway. Flask defaults to port 5000 if unset, causingECONNREFUSEDerrors"runtime_wiring.pyreadsint(os.environ.get("PORT", "8001"))— AutoMem's own default is 8001, and Flask's 5000 default is never reached.LOG_LEVEL| No |INFO| "Python logging level"LOG_LEVELappears nowhere in the repository.app.pycallsconfigure_logging(level=logging.INFO)with a hardcoded literal, andconfigure_loggingtakes the level as a keyword argument with no env lookup. SettingLOG_LEVELdoes nothing.INFOand how to actually change it.FLASK_ENV| No |production| "Flask environment mode"FLASK_ENVnorFLASK_DEBUGis referenced in any non-test source file.app.run()hardcodesdebug=False. Setting it has no effect.grep -rn "FLASK_ENV|FLASK_DEBUG" --include=*.pyreturns no non-test hits at8ff266eSEARCH_WEIGHT_RELEVANCE— "LLM-scored relevance (disabled by default)"memory["relevance_score"], which comes from the consolidation decay cycle (access patterns + age). No LLM is involved.JIT_ENRICHMENT_ENABLED— "Run enrichment inline on store (just-in-time)"jit_enrich_lightweight, which is wired in asjit_enrich_fnand invoked from the recall path for results the background worker has not enriched yet. It does not run on store.The
PORTfix closes out the last instance of the "Flask defaults to 5000" myth on this docs site — prior audits removed it fromoperations/troubleshooting,overview,deployment/railway,platforms/chatgpt, andplatforms/claude-web.Spot-checked and confirmed correct, left untouched: the three-source config-loading priority order (process env wins because
load_dotenv()does not override existing vars, project.envis loaded before~/.config/automem/.env);CLASSIFICATION_MODELdefaultgpt-4o-mini;RECALL_EXCLUDED_TYPESdefaultMetaPattern;RECALL_RELATION_LIMIT5; and theAUTOMEM_LOG_LEVELMCP-client row, which is genuinely read bysrc/index.ts.This page has no source-note block, so there were no permalinks to repin.
Verified against: automem@8ff266e62e65cb2e81719a765b05f64a2361a127
Verified against: mcp-automem@946f9e5ed1385b632efd2e5b250d064bcc4295e8
Questions
LOG_LEVEL"), which seemed more useful than deleting the section — but if you would rather drop the heading entirely, say so and I will.LOG_LEVELenv var be added to the service instead? The docs promising one suggests it was intended. That is a code change, not a docs fix, so it is out of scope here.Unverified
None — every row touched in this PR was located in source, and the two removals are backed by repo-wide absence rather than an inability to find the code.
Follow-ups
None on the variables audited. The tables were checked row-by-row against
automem/config.py; the remaining defaults matched.Generated by Claude Code