i generally have ~3-4 vscode oc terminal tabs going on things that are unlikely to touch each other, 1-2 on build mode, 1-2 on plan mode
- plan mode ones can be debugging, researching
- but I check on them every minute or two and make sure they're not being shit-stupid (trying random-ass things instead of methodically debugging) / stuck in a loop
- 80% of my prompting is "DRY" "consistent" "non-rigid" "single-source-of-truth" "[what's|double check this is] the best long-term proper architecture/solution"
if you close an opencode session and want to resume it a few days later to fix a bug it created or add a feature
- find the commit using git log or ptm bisect or whatever
- in the commit find openCodeSessionId: ses_2d957c6f0ffe8J2yZlzVAYU2nd
- run opencode -s ses_2d957c6f0ffe8J2yZlzVAYU2nd
in general, with experience, the more you "walter-white-changing-a-lightbulb" / "give-a-mouse-a-cookie" in your codebase the more productive you will be long-term & less productive short-term
- however: when working with agents, you should be careful about side-tracking to completely diff context. it's better to "brief summarize issue/repro for another agent incl rel eps" & pass that off to new opencode session
- then, when agent2 fixes it, resume agent1 w "^ fixed by another agent pls retry"
stay in plan mode until agent's questions stop or get dumbly trivial & give est LOC, then switch to build
make sure the agent gives you a loc est before switching to build
often at around 70% context just before compaction ask: "what are your best recs to improve code in-context per your agents.md"
agents adding redundant comments no matter how i change agents.md..
// Top donors by total donated
gqTopDonors(limit: Int): [DonorStats!]!