Problem
GCode always operates in the directory it was launched from. There's no way
to point it at another project without cd (and switching back), which
complicates editor/alias integration.
Proposed approach
- Add
gcode --cwd DIR (like -C in git) that os.chdirs before loading
config/.gcoderc and tools, so the banner and all tools reflect DIR.
- Resolve
.gcoderc lookup against the chosen directory.
Where to look
Acceptance criteria
gcode --cwd /some/project shows /some/project in the banner and tool calls operate there.
.gcoderc in that directory is honored.
Difficulty
Low/Medium — good first issue.
Problem
GCode always operates in the directory it was launched from. There's no way
to point it at another project without
cd(and switching back), whichcomplicates editor/alias integration.
Proposed approach
gcode --cwd DIR(like-Cin git) thatos.chdirs before loadingconfig/
.gcodercand tools, so the banner and all tools reflect DIR..gcoderclookup against the chosen directory.Where to look
gcode/cli.py:239-...(main) — startup order (env → config → model → tools).gcode/config.pyload_config(project_root=...)(in feat: add optional .gcoderc configuration file support #48).Acceptance criteria
gcode --cwd /some/projectshows/some/projectin the banner and tool calls operate there..gcodercin that directory is honored.Difficulty
Low/Medium — good first issue.