Docs: conda env name is `cf` / `circuitforge`, not `job-seeker` #62

New issue

Open

opened 2026-05-20 20:46:32 -07:00 by xenon · 0 comments

xenon commented

2026-05-20 20:46:32 -07:00

Member

Problem

Several places in CF documentation (including the org-level CLAUDE.md) still reference the old conda environment name job-seeker for running CF Python tools:

# Outdated:
conda run -n job-seeker <cmd>

# Correct:
conda run -n cf <cmd>
# or:
conda run -n circuitforge <cmd>

Scope

Places to audit and update:

/Library/Development/CircuitForge/CLAUDE.md — "Python env" section
Any README.md or setup docs in circuitforge-core that reference the conda env name
Any product-level CLAUDE.md files that inherited the old name

Notes

Also worth documenting the venv alternative for server/beta-host deployments that don't use conda — the job-seeker → cf rename invalidated a lot of copy, good time to add a venv path too
Discovered during xanderland.tv env setup (2026-05-21) where we used venv as the alternative path

## Problem Several places in CF documentation (including the org-level `CLAUDE.md`) still reference the old conda environment name `job-seeker` for running CF Python tools: ```bash # Outdated: conda run -n job-seeker <cmd> # Correct: conda run -n cf <cmd> # or: conda run -n circuitforge <cmd> ``` ## Scope Places to audit and update: - `/Library/Development/CircuitForge/CLAUDE.md` — "Python env" section - Any `README.md` or setup docs in `circuitforge-core` that reference the conda env name - Any product-level `CLAUDE.md` files that inherited the old name ## Notes - Also worth documenting the **venv alternative** for server/beta-host deployments that don't use conda — the `job-seeker` → `cf` rename invalidated a lot of copy, good time to add a venv path too - Discovered during xanderland.tv env setup (2026-05-21) where we used venv as the alternative path