continuedev / continuedev/continue
Impact of Cursor's Acquisition of Continue on existing customized traceability from session.json and autocomplete.jsonl files?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Before submitting your bug report
- I've tried finding an answer on the Continue docs site
- I'm not able to find an open issue that reports the same bug
- I've seen the troubleshooting guide on the Continue Docs
Relevant environment info
- OS: Windows
- Continue version:
- IDE version: VSCode
Description
This is not a bug report, but rather a question.
We have developed a customized AI traceability solution based on Continue's session.json and autocomplete.jsonl files. However, we understand that Continue has now been acquired by Cursor.
We would like to know whether these JSON files will continue to be available in the user profile(dev_data) in future releases, or if there are any planned changes or alternative mechanisms that we should be aware of for traceability.
To reproduce
No response
Log output
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.
Research direction
Review the Continue documentation and the handling of session.json and autocomplete.jsonl in the user profile (dev_data). The issue does not identify a code change or test; completion would require a maintainer decision about continued availability or an alternative traceability mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100