Skip to content

Conversation

@jwrhw7tueydwtt7575g
Copy link

@jwrhw7tueydwtt7575g jwrhw7tueydwtt7575g commented Jan 11, 2026

Description

[ What changed? Feel free to be brief. ]

AI Code Review

  • Team members only: AI review runs automatically when PR is opened or marked ready for review
  • Team members can also trigger a review by commenting @continue-review

Checklist

  • [] I've read the contributing guide
  • [] The relevant docs, if any, have been updated or created
  • [] The relevant tests, if any, have been updated or created

Screen recording or screenshot

[ When applicable, please include a short screen recording or screenshot - this makes it much easier for us as contributors to review and understand your changes. See this PR as a good example. ]

Tests

[ What tests were added or updated to ensure the changes work as expected? ]


Continue Tasks

Status Task Actions
▶️ Queued Create GitHub Issue (OS) View

Powered by Continue


Summary by cubic

Adds CLA enforcement and expands CI with new compliance checks, agent workflows, and IDE build/test pipelines. Also introduces .continue agent prompts and documentation/testing rules, and removes legacy Changie-based changelogs.

  • New Features

    • Enforce CLA signatures via updated workflow scoped to the main repo
    • Add workflows: compliance checks, CLI PR checks, general review, beta release, stale branch cleanup, VS Code build/E2E, JetBrains tests/releases
    • Add composite actions for setup, LLM-change detection, VS Code E2E, JetBrains tests, and VS Code extension builds
    • Add .continue prompts and rules for agents, docs standards, testing, UI themes, and LLM specificity
  • Refactors

    • Remove Changie config and per-extension CHANGELOG files
    • Update issue and PR templates with clearer guidance and community links
    • Tighten shared ESLint rules (e.g., no-misused-promises, no-negated-condition)
    • Simplify JetBrains release workflow inputs and channel handling

Written for commit b7ae5be. Summary will update on new commits.

sestinj and others added 30 commits December 5, 2025 17:07
…to-runloop-setup

Add docker.io and docker-compose to system setup dependencies
Add eslint@^8 to root package.json devDependencies to ensure npm
uses eslint 8.x instead of 9.x. The core package requires eslint@^8,
but @typescript-eslint/parser@8.x allows either eslint 8 or 9. Without
an explicit constraint, npm install was choosing eslint 9, causing the
lock file to be out of sync with core's requirements and breaking CI.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
…eprint-upload-workflow

Add GitHub workflow to upload Runloop blueprint on changes
…-service-restarts

Prevent service auto-start during apt install in runloop blueprint
…-blueprint-echo-to-printf

Combine policy-rc.d setup commands into single line in runloop blueprint
Ensures all new sessions have the usage tracking structure initialized
to prevent undefined field errors.

Co-authored-by: nate <nate@continue.dev>
Co-authored-by: nate <nate@continue.dev>
Co-authored-by: nate <nate@continue.dev>
…l-command-timeout-parameter

Add configurable timeout parameter to runTerminalCommand tool
Co-authored-by: nate <nate@continue.dev>
…er-dependencies

Add Dockerfile and remove Docker installation from system setup
…isical-cli

Add Infisical CLI installation to Runloop blueprint setup
…compose-to-runloop-setup

Add docker-compose-v2 to runloop blueprint dependencies
…on-cost-and-usage

Add comprehensive cost tracking with OpenAI pricing and session usage display
Snyk has created this PR to upgrade @tiptap/extension-history from 2.26.1 to 2.27.1.

See this package in npm:
@tiptap/extension-history

See this project in Snyk:
https://app.snyk.io/org/continue-dev-inc.-default/project/c5fb30df-a06c-44cb-83af-5ada5ff6e4a9?utm_source=github&utm_medium=referral&page=upgrade-pr
sestinj and others added 21 commits January 6, 2026 12:21
…e-copy-reimplement

fix: change 'Agent:' to 'Config:' in intro message and update tests
The "Update Check Run" step was interpolating step outputs directly into
JavaScript template literals, which breaks when the agent output contains
backticks, template literal interpolation sequences, or other special
characters that interfere with JS string parsing.

This caused failures like "SyntaxError: Unexpected identifier 'mobile'" when
the agent output contained multi-line text with certain keywords.

Fix by passing outputs as environment variables and accessing them via
process.env, which safely handles all string content without parsing issues.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…nts-js-parsing

fix: use env vars for safe string handling in continue-agents workflow
The Write job summary step had the same issue - backticks in the agent
output were being interpreted as bash command substitution, causing
'syntax error near unexpected token' failures.

Use environment variables and printf instead of echo to safely handle
all special characters in the output.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- continue-agents.yml: Use env var for agent name in Create Check Run step
  (prevents JS template literal breakage with backticks in filenames)

- run-continue-agent.yml: Use jq to construct JSON body instead of
  string interpolation (prevents JSON syntax errors when prompt contains
  quotes, newlines, backslashes, or other special characters)

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
fix: use env vars in Write job summary step for safe string handling
feat: allow selecting images using cmd+a
* Change title and description

* Add cloud agents definition

* Add comparison table for local v. cloud

* Add more targeted description

* Optimize card language

* Update description to include cloud agents

* Optimize mission control page for cloud agents

* More CA optimization

* Add early distinction

* Optimize for CA and remove references to UI elements no longer there.

* Clean up into to agents and optimize

* Optimize

* Shorten title and fix link

* Update Integrations with cloud agents

* Add top asked for cloud agent feature to GH docs

* Add FAQs to GitHub integration page

* Optimize metrics page for cloud agents

* Replace old new agent link

* Update docs/mission-control/metrics.mdx

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

* Update docs/agents/intro.mdx

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

* Update docs/agents/intro.mdx

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com>
…#9440)

Bumps [preact](https://github.com/preactjs/preact) from 10.27.1 to 10.28.2.
- [Release notes](https://github.com/preactjs/preact/releases)
- [Commits](preactjs/preact@10.27.1...10.28.2)

---
updated-dependencies:
- dependency-name: preact
  dependency-version: 10.28.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Changed banner content to highlight the new Agents page in Mission Control,
replacing the previous message about workflows and integrations.

Generated with [Continue](https://continue.dev)

Co-authored-by: BekahHW <BekahHW@users.noreply.github.com>
Co-authored-by: bekah-hawrot-weigel <bekah@continue.dev>
Co-authored-by: Continue <noreply@continue.dev>
- Renamed 'Slack Agent' to 'Agent for Slack' and updated copy across pages
- Updated nav links and redirects from /slack-agent to /slack
- Added safety disclaimer with privacy policy link
- Clarified connection/disconnection wording and support notes

Generated with [Continue](https://continue.dev)

Co-authored-by: dallin <dallin@continue.dev>
Co-Authored-By: Continue <noreply@continue.dev>
…ance-updates

docs: copy updates for Slack compliance
…ength-exceeded

fix(cli): context length tweaks and terminal output truncation
- Implement MCP server for dlt pipeline inspection and debugging
- Add 6 tools: inspect_pipeline, get_schema, query_destination, analyze_errors, scaffold_pipeline, review_schema_evolution
- Include pipeline discovery utilities and database connectors
- Add comprehensive test suite (26 tests, all passing)
- Add README with documentation and examples
- Support DuckDB and PostgreSQL destinations
- Read-only SQL query validation for safety
@jwrhw7tueydwtt7575g jwrhw7tueydwtt7575g requested a review from a team as a code owner January 11, 2026 09:48
@jwrhw7tueydwtt7575g jwrhw7tueydwtt7575g requested review from Patrick-Erichsen and removed request for a team January 11, 2026 09:48
@continue-staging
Copy link

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

@continue
Copy link
Contributor

continue bot commented Jan 11, 2026

All Green - Keep your PRs mergeable

Learn more

All Green is an AI agent that automatically:

✅ Addresses code review comments

✅ Fixes failing CI checks

✅ Resolves merge conflicts


Unsubscribe from All Green comments

@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Jan 11, 2026
Copy link
Contributor

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 2898 files

Note: This PR contains a large number of files. cubic only reviews up to 75 files per PR, so some files may not have been reviewed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:L This PR changes 100-499 lines, ignoring generated files.

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.