Extension: config write-back should respect existing config file location
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- tooling
Research direction
Start in vscode-extension/src/commands/instructions.ts and trace loadAgentrcConfig() to see how it resolves the root and .github/agentrc.config.json candidates. Update write-back to use the resolved existing location, creating the root file only when neither candidate exists. Done means write-back preserves the repository's existing config location.
Written by the indexing model from the issue text.
Description
The strategy write-back in vscode-extension/src/commands/instructions.ts always targets <repo>/agentrc.config.json, but loadAgentrcConfig() also supports .github/agentrc.config.json. If a repo uses the .github/ location, this silently creates a second config file, and future reads may not pick up the intended one.
Proposed: Check loadAgentrcConfig() resolution path to determine which candidate file exists, and update that one. Only create a new file at the root when neither exists.
Ref: PR #55 review comment instructions.ts
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 94
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 34
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/agentrc
-
agentic-workflows automation readiness
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
microsoft/agentrc#379 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/agentrc#372 · 2 reactions ·
Maintainers usually reply within 1 day
-
[aw] Detection RunsOpenagentic-workflows
Difficulty 5/5 Over a week Newbie friendliness 1/100
microsoft/agentrc#349 · 8 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
All issues in microsoft/agentrc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
answerLoops/answerLoops#345 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
siyuan-note/siyuan#20313 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LanternOps/breeze#8254 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
gofish-graphics/gofish-graphics#1084 ·
Maintainers usually reply within 1 day