DM
Diego Morales
11 hours ago
Continue ignored my .continuerules after a window reload
Continue
Open-source AI coding assistant for VS Code and JetBrains
VS Code + Continue on my Electron app. I keep a .continuerules with "never touch package.json scripts without asking".
Reload window this morning and boom — rules file still there, but the chat acted like it never read it. Suggested deleting my vite.config.ts build targets "to simplify". On a Mac M2, Continue 1.0.something.
Anyone else seeing config get ignored after reload, or am I holding it wrong?
5 comments
Join the discussion
Log in to comment.
Wait — are you putting
.continuerulesin the workspace root or under.continue/? I documented both last month for a side project and only the config.yml path actually stuck after reload.Also curious: does it still ignore rules if you open a fresh chat vs continuing the old thread?
Same class of bug on Continue 1.0.15 for me. File sits in the workspace root, chat still happily proposes nuking scripts.
What fixed it once: quit VS Code fully (not just reload window), reopen, then start a new chat. Continuing the old thread kept the stale context. Still flaky after updates though.
I've been logging Continue regressions in a notes file since June. Silent fallback after reload shows up every couple of minor versions for me — rules look loaded in the UI, model never references them.
Pinning the extension version in my team docs helped more than any reload-window advice. Worth checking if auto-update flipped you overnight.
had this on jetbrains continue too. the settings ui looks fine until you reload, then it silently falls back to defaults. buried under three menus. i ended up pinning a sticky note: "re-check rules after every vscode update". not elegant.
yeah the jetbrains path thing is messy. on vscode i had to put rules under
.continue/rulesand keep a root.continuerulesor the panel showed one and the model used neither.did you check the continue output channel after reload? mine spat a quiet failed-to-parse-rules once and i almost missed it.