Problem
explore and record write output to .opencli/ relative to cwd, while operate init correctly writes to ~/.opencli/clis/. This inconsistency pollutes project directories with opencli artifacts.
Current behavior
| Command |
Output path |
Correct? |
operate init |
~/.opencli/clis/<site>/ |
✅ |
explore |
cwd/.opencli/explore/<site>/ |
❌ |
record |
cwd/.opencli/record/<site>/ |
❌ |
Source references:
explore.js:329: path.join('.opencli', 'explore', siteName) — relative path
record.js:625: path.join('.opencli', 'record', site) — relative path
record has --out <dir> as workaround, but explore doesn't expose outDir in CLI args (only in code)
Expected behavior
Default output for all commands should go to ~/.opencli/:
~/.opencli/explore/<site>/
~/.opencli/record/<site>/
This is consistent with operate init writing to ~/.opencli/clis/ and keeps project directories clean.
Workaround
record: opencli record <url> --out ~/.opencli/record/<site>
explore: no workaround (need to cd ~/.opencli first)
Problem
exploreandrecordwrite output to.opencli/relative to cwd, whileoperate initcorrectly writes to~/.opencli/clis/. This inconsistency pollutes project directories with opencli artifacts.Current behavior
operate init~/.opencli/clis/<site>/explorecwd/.opencli/explore/<site>/recordcwd/.opencli/record/<site>/Source references:
explore.js:329:path.join('.opencli', 'explore', siteName)— relative pathrecord.js:625:path.join('.opencli', 'record', site)— relative pathrecordhas--out <dir>as workaround, butexploredoesn't exposeoutDirin CLI args (only in code)Expected behavior
Default output for all commands should go to
~/.opencli/:~/.opencli/explore/<site>/~/.opencli/record/<site>/This is consistent with
operate initwriting to~/.opencli/clis/and keeps project directories clean.Workaround
record:opencli record <url> --out ~/.opencli/record/<site>explore: no workaround (need tocd ~/.openclifirst)