Continue is an open-source AI code assistant designed to enhance coding experiences within IDEs like VS Code and JetBrains. It allows integration of various AI models for custom autocomplete and chat functionalities. The project is actively developed, with significant community engagement and contributions.
Summary
Quantified Reports
Detailed Reportscore/autocomplete/completionProvider.ts): High complexity suggests a need for refactoring or additional documentation.| Timespan | Opened | Closed | Comments | Labeled | Milestones |
|---|---|---|---|---|---|
| 7 Days | 35 | 17 | 49 | 1 | 1 |
| 30 Days | 142 | 60 | 238 | 1 | 1 |
| 90 Days | 295 | 128 | 801 | 2 | 2 |
| All Time | 1478 | 934 | - | - | - |
Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.
.png?size=50)
.png?size=50)
.png?size=50)
.png?size=50)
.png?size=50)
.png?size=50)
.png?size=50)
.png?size=50)
| Developer | Avatar | Branches | PRs | Commits | Files | Changes |
|---|---|---|---|---|---|---|
| Nate Sesti |  |
15 | 3/4/0 | 91 | 160 | 34257 |
| Patrick Erichsen |  |
14 | 29/28/1 | 67 | 154 | 14147 |
| Adam Shedivy (ajshedivy) | 1 | 1/1/0 | 2 | 5 | 247 | |
| Donghwan Jeung (DongjaJ) | 1 | 1/1/0 | 2 | 6 | 25 | |
| Kangmoon Seo (KangmoonSeo) | 2 | 3/2/1 | 2 | 1 | 24 | |
| Lukas Kreussel (LLukas22) | 1 | 1/1/0 | 1 | 1 | 15 | |
| Sherman Boyd (shermanhuman) | 1 | 4/1/3 | 1 | 2 | 14 | |
| Steve Rhoades |  |
1 | 3/2/0 | 2 | 1 | 7 |
| Shigma (shigma) | 1 | 2/1/1 | 1 | 2 | 5 | |
| Lester Hairston (eagle3y3) | 1 | 5/3/1 | 1 | 1 | 4 | |
| Chris Lane (ChrisLane) | 1 | 1/1/0 | 1 | 1 | 4 | |
| None (FallDownTheSystem) | 1 | 1/1/0 | 1 | 1 | 4 | |
| Yuya Kanai (Cactice) | 1 | 1/1/0 | 1 | 1 | 2 | |
| None (lolikung) | 1 | 2/1/1 | 1 | 1 | 2 | |
| Yury Sokov (Yurzs) | 0 | 1/0/1 | 0 | 0 | 0 | |
| None (mq200) | 0 | 0/1/0 | 0 | 0 | 0 | |
| Ty Dunn (TyDunn) | 0 | 1/0/1 | 0 | 0 | 0 | |
| None (qaz-ttt) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Andreas Franzén (triptec) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Simon M. (simon376) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Ankita Jaat (ankutjaat) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Kevin Abestilla (kevin1193) | 0 | 2/0/1 | 0 | 0 | 0 | |
| None (ChadDa3mon) | 0 | 2/0/2 | 0 | 0 | 0 | |
| Shawn Smith (chezsmithy) | 0 | 2/1/1 | 0 | 0 | 0 | |
| Samuel Bubán (Mahrkeenerh) | 0 | 0/1/0 | 0 | 0 | 0 | |
| You Jiacheng (YouJiacheng) | 0 | 1/1/0 | 0 | 0 | 0 | |
| Raja Jamwal (raja-jamwal) | 0 | 0/0/1 | 0 | 0 | 0 | |
| None (dhlidongming) | 0 | 1/0/1 | 0 | 0 | 0 | |
| Priyash (priyashpatil) | 0 | 0/0/1 | 0 | 0 | 0 | |
| refactorthis (refactorthis) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Tijs Zwinkels (tijszwinkels) | 0 | 1/1/0 | 0 | 0 | 0 | |
| Freerk Minnema (freerkminnema) | 0 | 1/1/0 | 0 | 0 | 0 | |
| Justin Milner (justinmilner1) | 0 | 0/1/0 | 0 | 0 | 0 | |
| None (dependabot[bot]) | 0 | 3/0/3 | 0 | 0 | 0 | |
| Santiago Basulto (santiagobasulto) | 0 | 1/0/0 | 0 | 0 | 0 | |
| Sambhav Dixit (sambhavnoobcoder) | 0 | 1/0/0 | 0 | 0 | 0 |
PRs: created by that dev and opened/merged/closed-unmerged during the period
| Risk | Level (1-5) | Rationale |
|---|---|---|
| Delivery | 4 | The project faces significant delivery risks due to a backlog of 544 open issues, with more issues being opened than closed over recent periods. The presence of unresolved integration problems with IDEs like JetBrains and VS Code (#2436, #2421) and configuration challenges (#2391, #2168) further exacerbate these risks. Additionally, the backlog of open pull requests and ongoing build script issues highlight potential delays in delivery timelines. |
| Velocity | 4 | Velocity is at risk due to the high volume of unresolved issues and pull requests. The disparity in commit activity among team members suggests potential bottlenecks, with key contributors like Nate Sesti and Patrick Erichsen driving most of the progress. The presence of unresolved technical debt and dependency risks in PRs like #2282 and #2416 could further slow down development. |
| Dependency | 3 | Dependency risks are moderate, with some pull requests indicating reliance on external systems or libraries that may fail. PR #2282's integration of PiecesOS LLM highlights potential compatibility questions, while ongoing configuration challenges suggest existing dependencies may not be fully stable. |
| Team | 3 | The team faces moderate risks related to workload distribution and communication. Key developers are contributing significantly more than others, which could lead to burnout or conflict. However, active community engagement through Discord suggests positive team dynamics if managed well. |
| Code Quality | 3 | Code quality is generally maintained through active review processes, but recurring issues in autocomplete functionality (#2061, #2073) and minor documentation corrections suggest areas for improvement. The need for frequent fixes indicates underlying quality concerns that need addressing. |
| Technical Debt | 4 | Technical debt is a significant concern, with ongoing fixes required for integration issues and build processes. The presence of unresolved technical debt in PRs like #2416 and configuration challenges (#2391) indicates a need for better management to prevent further accumulation. |
| Test Coverage | 3 | Test coverage appears adequate but not comprehensive. While unit tests are included in some PRs like #2424, the frequent need for fixes suggests that testing may not catch all issues initially. More robust testing practices could help reduce recurring problems. |
| Error Handling | 3 | Error handling is moderately effective, with attention given to fixing errors as they arise (e.g., PR #2424). However, ongoing bugs and the need for error handling improvements indicate room for enhancement to ensure all errors are caught and reported efficiently. |
Recent GitHub issue activity for the Continue project shows a high volume of both open and closed issues, indicating active development and community engagement. Notably, there are recurring themes around integration issues with different IDEs, configuration challenges, and enhancements for AI model support.
Integration Issues: Many users report problems with integrating Continue into various IDEs, particularly JetBrains and VS Code. Issues like #2390 and #2178 highlight difficulties with slash commands and cursor visibility in JetBrains.
Configuration Challenges: Several issues (#2391, #2168) relate to configuring models and handling network requests, especially when using local or remote models like Ollama.
Autocomplete Functionality: Autocomplete is a frequent topic, with issues like #2061 and #2073 discussing its behavior within different contexts or languages.
Indexing Problems: Indexing errors are common, as seen in issues like #1964 and #2099, where large files or specific configurations lead to failures.
Enhancements and Feature Requests: There is a strong demand for new features, such as improved support for private clusters (#2404) and enhanced changelog generation (#2064).
Community Engagement: The project actively engages with its community through Discord, as evidenced by many users referencing discussions there before filing issues.
These recent issues reflect ongoing challenges with IDE integration and model configuration, which are critical for maintaining the tool's flexibility and usability across different environments.
prepackage.js script. Needs further debugging.mentionlist need resolution.config.ts not loading in Jetbrains Editors (Merged)The project is actively maintained with several open pull requests focusing on bug fixes, feature enhancements, and documentation improvements. Notably, there are duplicate efforts in typo corrections (#2433 and #2434), which should be consolidated. The addition of new features like Discord integration (#2425) and speech-to-text functionality (#2047) indicates ongoing innovation. However, some PRs require more feedback or testing before they can be merged safely. The project continues to evolve with community contributions and active development.
.github/workflows/auto-assign.yamlissues and pull_request events.ubuntu-latest.pozil/auto-assign-issue@v2 for auto-assignment.docs/docs/customize/tutorials/custom-code-rag.mddocs/static/schemas/config.json$ref for reusability.extensions/intellij/src/main/resources/config_schema.jsonconfig.json, tailored for IntelliJ specifics.extensions/vscode/config_schema.jsonextensions/vscode/continue_rc_schema.jsoncore/autocomplete/completionProvider.tscore/index.d.tsOverall, the codebase demonstrates a strong emphasis on structure, consistency, and clarity. The use of TypeScript enhances type safety and maintainability. Documentation within code files is generally good but could be improved in more complex areas to aid understanding.
## Development Team and Recent Activity
### Team Members and Their Activities
- **Nate Sesti (sestinj)**
- Frequent contributor with multiple merges and fixes.
- Worked on various features including auto-assignment, schema config fixes, onboarding refactor, and documentation updates.
- Collaborated with Patrick Erichsen, Steve Rhoades, and others.
- **Patrick Erichsen (Patrick-Erichsen)**
- Involved in creating and updating auto-assign workflows.
- Contributed to documentation refactoring and onboarding improvements.
- Worked closely with Nate Sesti on several features.
- **Steve Rhoades (steverhoades)**
- Focused on fixing documentation issues.
- Collaborated with Nate Sesti for documentation corrections.
- **Ty Dunn (TyDunn)**
- Made final edits and contributed to CI fixes.
- **Yury Sokov (Yurzs)**
- Added remote config sync job to IDEA.
- **Anders Barfod (baffioso)**
- Updated API types and provided JSON examples.
- **Adarsh Varshney (adarshdotexe)**
- Added NvidiaEmbeddingsProvider.
- **Tuowen Zhao (ztuowen)**
- Worked on SambaNova Cloud API integration.
- **Radha Jain (radhajain)**
- Enabled custom domains for GitHub Issue provider.
### Patterns and Themes
1. **Collaboration:** There is significant collaboration among team members, especially between Nate Sesti and Patrick Erichsen, indicating a strong team dynamic focused on continuous improvement and feature enhancement.
2. **Documentation and Configuration:** A considerable amount of work has been dedicated to improving documentation and configuration schemas, reflecting a focus on usability and developer experience.
3. **Feature Development:** The team is actively working on enhancing existing features like onboarding, autocomplete, and context providers while also integrating new capabilities such as NvidiaEmbeddingsProvider and SambaNova Cloud API.
4. **Bug Fixes:** Regular bug fixes are being implemented, particularly in documentation and configuration areas, ensuring the project remains stable and reliable.
5. **Continuous Integration:** Updates to CI workflows suggest an ongoing effort to streamline development processes and maintain code quality.
Overall, the development team is actively engaged in both maintaining existing functionalities and expanding the project's capabilities through collaborative efforts.