Skip to content

Next steps: publish + verify WSL OpenCode setup #13

Description

@dtsong

Next steps

  • Initialize this directory as a git repo, set the correct GitHub remote, and push main
    • If the intended repo name is opencode-codex-wsl-setup, create/rename the GitHub repo accordingly
  • Commit the initial scaffold (installer, templates, skills, commands, plugins)
  • Verify OpenCode discovery + safety posture in WSL
    • opencode debug paths
    • opencode debug config
    • opencode debug skill
    • Run /wsl-check (after installing commands)
  • Verify installer flows
    • ./install.sh (skills-only, non-invasive)
    • ./install.sh --preset full --with-config (opt-in global config + plugins + commands)
    • ./install.sh --uninstall removes only manifest-matched files
  • Validate plugins in a real WSL session
    • Compaction: confirm compacted context keeps decisions/next steps (plugins/compaction-handover.ts)
    • Notifications: confirm Windows toast notifications fire from WSL (plugins/notifications.ts)
  • Add a real workspace hint bundle (optional)
    • Create workspaces/<slug>/HINTS.md (or global ~/.config/opencode/workspaces/<slug>/HINTS.md)
    • Confirm plugins/workspace-context.ts injects pointers only (no large dumps)
  • Port proven skills/patterns from dtsong/claude-code-wsl-setup
    • Keep SKILL.md small; move depth into references/*.md for progressive loading

Notes

  • Model should be set via env for portability: OPENCODE_MODEL=openai/gpt-5.3-codex
  • API key should be env-only: OPENAI_API_KEY=...

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions