Δdeltalog

AI 코딩 도구,
이번엔 뭐가 바뀌었나

Claude Code, Codex 같은 개발 도구의 릴리스 노트를 한국어로 요약하고, 중요한 변경부터 보여줍니다.

도구 최신 버전

필터 2
9월 23일 (수)
CursorRollouts and Security Review26일 전 코드 배포 상태를 감시하는 Rollouts와 보안 검토를 수행하는 Security Review 봇을 출시한다 외 3개 +4 ●●●●●
  • + 코드 배포 상태를 감시하는 Rollouts와 보안 검토를 수행하는 Security Review 봇을 출시한다 # Git·연동
    원문

    Rollouts and Security Review: Today we're launching two Cursor bots for the last mile of shipping code. Rollouts watches every change as it deploys and reports its health per environment. Security Review reports exploitable bugs on every pull request. Both are available today on Teams and Enterprise plans.

  • + 풀 리퀘스트 배포 변경 사항을 모니터링하고 환경별 상태를 보고하는 Rollouts 기능을 추가한다 # Git·연동
    원문

    Rollouts: Rollouts attaches a monitor to every pull request and watches the change as it deploys, reporting change health per environment: verified healthy, regression detected, or inconclusive. It's the Cursor version of Firetiger Change Monitors, rebuilt with the Bot Development Kit. Enable it from the dashboard and connect source control, your deploy system, and your telemetry provider. Rollouts starts watching on the next pull request. When a pull request opens, Rollouts reads the diff and the systems it touches, then writes a monitoring plan as a PR comment. The plan lists the risks it identified, the effect the change is meant to have, the signals it will check, and any gaps in instrumentation that would make the change hard to verify. Edit the plan in the PR and Rollouts uses your version. Rollouts wakes on deploy events for the change's commit and runs the plan against your log

  • + 풀 리퀘스트에서 악용 가능한 버그를 찾아 검토 댓글을 남기는 Security Review 기능을 추가한다 # Git·연동
    원문

    Security Review: Security Review is available today. It reads every pull request in the context of the codebase and posts one review comment reporting exploitable bugs. Style and quality stay with Bugbot. Security Review comment on a pull request reporting an exploitable bug with a severity and proposed fix Enable it from the dashboard for the repositories you want reviewed. Draft PRs are skipped. Security Review looks for injection across SQL, command, and template surfaces, along with authentication and authorization bypasses, including checks that a refactor stopped running. It also flags secrets and credentials committed to source, SSRF and unvalidated redirects, unsafe deserialization, and dependency changes that introduce known vulnerabilities. It traces where user input enters and what it passes through. Each finding carries a severity, the attack path, and a proposed fix. Dismi

외 1개 항목은 원문에서 볼 수 있습니다.

AI가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.

변경 사항 페이지 원문 보기 ↗
9월 10일 (목)
CursorCursor Projects39일 전 Slack 채널이나 PR을 모니터링하고 자동으로 작업을 시작하는 구독 기능을 추가한다 외 3개 +4 ●●●●●
  • + Slack 채널이나 PR을 모니터링하고 자동으로 작업을 시작하는 구독 기능을 추가한다 # Git·연동
    원문

    Subscriptions: Tell the coordinator agent to watch a Slack channel, run on a schedule, or follow all your PRs. This way it can take action based on signals it detects, without waiting for your prompt. Connect Slack and point it at a bug-report channel, and it starts delegating each time a bug comes in. Projects are available in beta and rolling out to all users starting today.

외 3개 항목은 원문에서 볼 수 있습니다.

AI가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.

변경 사항 페이지 원문 보기 ↗
8월 17일 (월)
CursorOrigin Code Hosting2개월 전 GitHub 저장소를 Cursor에 연결하여 동기화하고 조회할 수 있게 한다 외 6개 +7 ●●●●●
  • + GitHub 저장소를 Cursor에 연결하여 동기화하고 조회할 수 있게 한다 # Git·연동
    원문

    Bring your GitHub repos: Your GitHub repos can sit alongside the ones Cursor hosts. Connect GitHub to Cursor, pick your org, and you'll see the repos you can sync. Select one and Cursor pulls it in. You choose what gets synced and can disconnect a repo at any time. Anyone with read or write access to a synced repo can view it in Cursor too. Synced repos update in real time. Browse, search, and pull from the copy in Origin. For synced repos, GitHub stays the source of truth: pushes keep going to GitHub, and Origin mirrors the result. Icons next to each repo name tell you which ones Cursor hosts and which came from GitHub.

  • + 저장소마다 pull request를 열고 검토하며 양방향으로 동기화할 수 있게 한다 # Git·연동
    원문

    Pull requests: Every repo has pull requests. Open one to see the timeline, commits, checks, and files changed. Review the diff, leave comments, and merge. Pull requests on synced repos sync both ways: comment in Cursor and it posts to GitHub, react or reply on GitHub and it shows up in Cursor within seconds. Got a review assigned to you on GitHub? Review and merge it from Cursor.

외 5개 항목은 원문에서 볼 수 있습니다.

AI가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.

변경 사항 페이지 원문 보기 ↗
7월 17일 (금)
CursorImprovements to Cursor in Slack3개월 전 Slack 연동 Cursor가 시작 전 계획을 공유하고 멀티 리포 환경 및 채널과 스레드를 지원한다 외 3개 +4 ●●●●●
  • + Slack 연동 Cursor가 시작 전 계획을 공유하고 멀티 리포 환경 및 채널과 스레드를 지원한다 # Git·연동
    원문

    Improvements to Cursor in Slack: Cursor in Slack now shares a plan before it starts, runs in multi-repo environments, and can work across channels and threads.

  • + Slack에서 멀티 리포 환경을 지원하고 작업 중 리포지토리 전환을 요청할 수 있게 한다 # Git·연동
    원문

    Multi-repo environment support: From Slack, Cursor can now start in a named multi-repo environment instead of a single default repository. If your frontend, backend, and shared code live in separate repos, Cursor reads your request and targets the environment that gives it access to all of them. Mid-task, when Cursor needs a repo outside the current environment, it prompts you with a **Switch repository** button. Click it, choose the repo or environment, and Cursor picks up right where it left off.

외 2개 항목은 원문에서 볼 수 있습니다.

AI가 만든 요약입니다. 원문과 다르면 오류 제보해 주세요.

변경 사항 페이지 원문 보기 ↗