Dylan Di Filippo
Dylan Di FilippoAI journal

The background.

Understand what changes. Choose what deserves a test.

Documentation and announcements without an established launch date are kept here, not presented as releases of a particular week.

Understand what changes.

Public sources. Verified facts. Analysis kept separate from announcements.

No verified stories in this selection. This does not imply there was no news.

Choose what deserves a test.

Public sources. Verified facts. Analysis kept separate from announcements.

2 stories

CursorCoding

Cursor Projects: same shift towards continuous work

Cursor also offers a coordination conversation with agents and event subscriptions. The competition moves towards sustainable execution and shared context.

Beta · conditions to be checked

Facts, analysis and limits

Verified facts

  • Projects assigns tasks to a coordinator that delegates to agents, shares context and can react to pull requests, Slack or schedules.
  • Cloud is the default mode, with local agents for machine needs. The blog announces a progressive beta.
  • The email received talks about paid plans, while the blog talks about a deployment to all users: the exact scope of access must be verified before purchase.

What changes

Compare with Claude Projects and Codex on the same migration: supervision, quality of PR, recovery after blocking and real limits. Avoid adding a subscription only to follow the trend.

Practical implication

Monitor or test with existing access; clarify conditions before subscription.

Availability

Beta; divergence between email and blog on the access perimeter. Do not conclude that usage is free.

Limits and uncertainty

The PR gains announced by Cursor are not an independent measure of quality or delivered value.

Context only: newsletter signal of 23 September. The primary source is dated 10 September; do not present this mention as a launch of the week of 21.

Cursor Projects : annonce officielle ↗
Read full article →
AnthropicCoding

Claude Code Projects: a coordinator above the sessions

The novelty is coordination: shared context, tasks distributed in threads and view of work completed or blocked. It is not just a conversation folder.

Progressive Beta Pro / Max

Facts, analysis and limits

Verified facts

  • Projects co-ordinates lasting work in a conversation, then launches parallel threads, usually in cloud sessions.
  • Current documentation describes a gradual Pro/Max beta, not yet Team/Enterprise. Cloud threads continue while the computer is closed; local threads need an awake machine.
  • Projects uses the same usage limits as other Claude Code sessions and can consume them faster with greater parallelism.

What changes

Relevant for a migration or a set of related tasks. For a one-off bug, a conventional session remains simpler and easier to control.

Practical implication

Test on a limited project, with separate branches and no push without approval.

Availability

Beta Pro/Max progressive, with waiting list. Rollout starts with accounts that have used cloud sessions, without existing projects in the Claude or Cowork chat. Unverified personal access.

Limits and uncertainty

The documentation confirms the function, but does not date its launch. The date of the 18 September signal is not supported in the pilot's archive.

Context only: documentation reviewed on September 30. The September 18 newsletter signal is not corroborated in this pilot's archive; the current documentation is undated.

Claude Code Projects : documentation ↗
Read full article →