anomalyco / anomalyco/opencode
[FEATURE]: Default starting directory to ~/Documents/OpenCode/Projects/Default Project with plugin home
Open
@Hona is already working on this.
Since Aug 29, 2026.
- Dominant language
- TypeScript
- Stars
- 209k
- Forks
- 27.5k
- PR merge metrics
- PR metrics pending
Description
Summary
- I have searched for existing issues before filing this
OpenCode currently starts in an arbitrary or user-specified directory. This issue requests changing the default starting directory to a structured path that supports plugin development and project organization from day one.
Problem
- No sensible default workspace —
User/Documents/OpenCode/Default Projectis a generic placeholder; users always land in an empty directory with no project context - No home for custom plugins —
file://plugins have no conventional location; users scatter them across the filesystem - First-run experience friction — new users have no pre-structured workspace to orient themselves
Proposed Solution
Change the default starting directory to:
~/Documents/OpenCode/Projects/Default Project/
With a sibling plugins/ directory at the OpenCode/ level:
~/Documents/OpenCode/
├── Projects/
│ └── Default Project/ ← session workspace root
└── plugins/ ← custom plugin home
├── my-plugin/
└── another-plugin/
Benefits:
OpenCode/isolates all OpenCode-related work under DocumentsProjects/signals active work, not a scratch directoryDefault Project/provides the same "start here" entry pointplugins/gives custom/coded plugins a clear, discoverable home
Related
- #42536 — "OPENCODE_INSTALL_DIR not respected" (adjacent: runtime dir vs workspace dir)
- #43173 — "folder picker search anchored to home dir" (related: directory navigation UX)
OS
Cross-platform (all clients).
🦙 Creative Monkey at FrenzyPenguin Media — open-source security hardening & privacy tools
Contributor 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.
Assessment
This issue has not been assessed yet.