Workspace blocks added feature but doesn’t work

[fradav]

Before submitting your bug report

• [x] I believe this is a bug. I'll try to join the Continue Discord for questions
• [x] I'm not able to find an open issue that reports the same bug
• [x] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: macos
- Continue version: 1.1.24
- IDE version: 1.99.3
- Model: ollama://mistral-small3.1:latest

Description

Since the 1.1.24 version and I believe commit https://github.com/continuedev/continue/commit/c59d923508a24442dccacfb190a6c51f93557c39, there is the possibility to add workspace docs/rules/models/mcpServers blocks. The issue is that they don’t do anything, they don’t appear in the list of available docs/rules/models/mcpServers. Workaround : local full assistant file in workspace still works.

To reproduce

No response

Log output

[AlkineHotel]

Seconded. Does nothing. Very very broken release altogether. The yaml config is inconsistent too. Your documentation provides keys that are not accepted and then causes failures.

From https://docs.continue.dev/customize/deep-dives/rules

rules:

• Always annotate Python functions with their parameter and return types

• name: TypeScript best practices rule: Always use TypeScript interfaces to define shape of objects. Use type aliases sparingly. globs: "**/*.{ts,tsx}"

• name: TypeScript test patterns rule: In TypeScript tests, use Jest's describe/it pattern and follow best practices for mocking. globs:

  • "src/**/*.test.ts"
  • "tests/**/*.ts"

• uses: myprofile/my-mood-setter with: TONE: concise

Copy paste straight on from documentation. No such key as globs, though. Save file. Rule does not show up, but oh hey, now everything is broken.

[Igorgro]

Having the same problem. Adding rules to .continue/rules directory in project root does nothing

[sestinj]

This should now be solved as of a few releases ago. I think the core of the problem was that we released documentation describing features that weren't in stable release until a week after they were visible in the docs. We will be more careful to avoid this in the future

[github-actions[bot]]

This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.

[github-actions[bot]]

This issue was closed because it wasn't updated for 10 days after being marked stale. If it's still important, please reopen + comment and we'll gladly take another look!