Skip to content

Changelog: move the fixes 15.1.0 didn't ship, and note the Cursor skill fix #2065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kjgbot wants to merge 1 commit into from
Closed

Changelog: move the fixes 15.1.0 didn't ship, and note the Cursor skill fix #2065

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 13 additions & 9 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,19 @@ All notable changes to Agent Relay will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]
## [Unreleased - Patch]

### Fixed

- `relay init` finds the messaging skill it installs for Cursor, so it no longer warns that the install failed, and `relay init --uninstall` removes it.

@cubic-dev-ai cubic-dev-ai Bot Nov 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P3: This bullet covers two behaviors: the install warning and uninstall. Split it so each gets its own impact-first bullet.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At CHANGELOG.md, line 12:

<comment>This bullet covers two behaviors: the install warning and uninstall. Split it so each gets its own impact-first bullet.</comment>

<file context>
@@ -5,7 +5,19 @@ All notable changes to Agent Relay will be documented in this file.
+
+### Fixed
+
+- `relay init` finds the messaging skill it installs for Cursor, so it no longer warns that the install failed, and `relay init --uninstall` removes it.
+- Codex agents that `relay serve` spawns now run the installed Codex app-server build whenever there is one, instead of the `codex` command on `PATH`.
+- Follow-up messages to Codex agents that `relay serve` spawns reach them through that same Codex build.
</file context>
Suggested change
- `relay init` finds the messaging skill it installs for Cursor, so it no longer warns that the install failed, and `relay init --uninstall` removes it.
- `relay init` no longer warns that the messaging skill install failed for Cursor.
- `relay init --uninstall` removes the messaging skill it installed for Cursor.

- Codex agents that `relay serve` spawns now run the installed Codex app-server build whenever there is one, instead of the `codex` command on `PATH`.
- Follow-up messages to Codex agents that `relay serve` spawns reach them through that same Codex build.
- A Claude Code session renamed on the relay is told its current name and address when it starts, not the name it first registered under.
- Choosing to upload a session again no longer re-uploads its unchanged history after `relay serve` restarts.
- Cursor CLI messaging hooks that setup installed before Cursor's first chat now show as installed and can be turned on or off.

@cubic-dev-ai cubic-dev-ai Bot Nov 3, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

P3: setup is ambiguous here and hides the command that installs these hooks. Name relay init so users can identify the affected workflow.

(Based on your team's feedback about naming concrete commands in changelog entries.) [6ebf7783-b19d-4605-9359-73ead75b2cfe]

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. When an issue isn't valid or won't be fixed in this PR, reply in its thread with the reason and then resolve the thread. At CHANGELOG.md, line 17:

<comment>`setup` is ambiguous here and hides the command that installs these hooks. Name `relay init` so users can identify the affected workflow.

(Based on your team's feedback about naming concrete commands in changelog entries.) [6ebf7783-b19d-4605-9359-73ead75b2cfe]</comment>

<file context>
@@ -5,7 +5,19 @@ All notable changes to Agent Relay will be documented in this file.
+- Follow-up messages to Codex agents that `relay serve` spawns reach them through that same Codex build.
+- A Claude Code session renamed on the relay is told its current name and address when it starts, not the name it first registered under.
+- Choosing to upload a session again no longer re-uploads its unchanged history after `relay serve` restarts.
+- Cursor CLI messaging hooks that setup installed before Cursor's first chat now show as installed and can be turned on or off.
+- Turning uploads Off for a session you connected yourself keeps it off after `relay serve` restarts.
+- A session whose upload was deleted from Cloud no longer rejoins the relay by itself.
</file context>
Suggested change
- Cursor CLI messaging hooks that setup installed before Cursor's first chat now show as installed and can be turned on or off.
- Cursor CLI messaging hooks that `relay init` installed before Cursor's first chat now show as installed and can be turned on or off.

- Turning uploads Off for a session you connected yourself keeps it off after `relay serve` restarts.
- A session whose upload was deleted from Cloud no longer rejoins the relay by itself.
- Devin agents started on macOS with `relay fleet spawn devin` or an agent's spawn request now get every message; one that arrived a moment after its connection opened could be lost.

## [15.1.0] - 2026-11-03

Expand All @@ -28,14 +40,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

- `cloud integration connect` identifies unsupported providers and points to catalog lookup on the same Cloud endpoint.
- `relay serve` delivers messages to agents more reliably and finds their sessions more consistently.
- Codex agents that `relay serve` spawns now run the installed Codex app-server build whenever there is one, instead of the `codex` command on `PATH`.
- Follow-up messages to Codex agents that `relay serve` spawns reach them through that same Codex build.
- A Claude Code session renamed on the relay is told its current name and address when it starts, not the name it first registered under.
- Choosing to upload a session again no longer re-uploads its unchanged history after `relay serve` restarts.
- Cursor CLI messaging hooks that setup installed before Cursor's first chat now show as installed and can be turned on or off.
- Turning uploads Off for a session you connected yourself keeps it off after `relay serve` restarts.
- A session whose upload was deleted from Cloud no longer rejoins the relay by itself.
- Devin agents started on macOS with `relay fleet spawn devin` or an agent's spawn request now get every message; one that arrived a moment after its connection opened could be lost.

## [15.0.2] - 2026-11-01

Expand Down
Loading