Skip to content

Release v2.3.1 - #55

Merged
Alex375 merged 5 commits into
mainfrom
dev
Sep 18, 2026
Merged

Alex375 merged 5 commits into
mainfrom
dev

Conversation

@Alex375

@Alex375 Alex375 commented Sep 16, 2026

Copy link
Copy Markdown
Owner

Release v2.3.1. Voir les commits de dev depuis la dernière release.

  • fix(artifacts): recognize the claude 2.1.272 artifact URL shape

🤖 Generated with Claude Code

Alex375 and others added 5 commits September 16, 2026 21:17
claude 2.1.272 moved hosted artifacts from
https://claude.ai/code/artifact/<uuid> to https://claude.ai/artifact/<id>.
The URL regex only matched the old shape, so every inline card read
"Unavailable" and prose artifact links rendered as bare anchors.
Accept both shapes (older transcripts keep the old URL), and share one
isArtifactPublish predicate between the inline card and the chip so the
new asset uploads (asset:true + file_path) never render as an artifact.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…aude Code

The settings rail had grown to 13 top-level tabs, several of them a single
page, and one of them ("Behavior") holding nothing but Claude-only prefs while
sitting outside the Claude Code tab. Reorganise around one rule: a tab is a
top-level CONCERN, sub-tabs carry the rest.

The rail is now 9 tabs:

- General (Accounts · System) — who the agents sign in as, and what the app may
  do to this machine. Absorbs the old Accounts tab; keeps the About block.
- Display (Appearance · Thread · Durations · Composer · Models · Order) — a new
  tab for everything the app SHOWS. Absorbs the old General → Display sub-tab,
  the whole Conversation tab (Markdown folded into Thread), the Durations
  sub-tab, and the top-level Reordering tab.
- Claude Code (Instructions · Behavior · Helpers) — gains sub-tabs, and takes
  over the old top-level "Behavior" tab. Output style writes
  `~/.claude/settings.json`, and the bypass unlock arms a `claude` CLI flag:
  both are Claude-only and do nothing for a Codex conversation, so they now
  follow this tab's `needsClaude` visibility. Accepted consequence: with no
  Claude account signed in, neither is reachable.
  Routing and spend stay on ONE page — the spend table is the bill for the
  routing above it.

Plumbing that had to follow:

- `openSettings` takes an optional sub-tab, so the auth warning bar still
  deep-links to General → Accounts instead of dropping the user on the machine
  card. Passing no sub leaves the remembered sub-tabs alone.
- The 37 moved entries of the settings search index are remapped; the unit test
  that catches a result pointing at a sub-tab nobody renders stays green.
- `DisplayPrefs` split into `AppearancePrefs` / `ThreadPrefs` / `MotionPrefs`,
  and `ClaudeCodeSection` now exports two groups instead of a page — so
  `SettingsPanel` remains the single place describing the panel's shape (same
  pattern as `ControlSection`).

No pref, toggle or default changes behaviour: this moves where settings live,
not what they do.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
When a background task finished, its terminal task_notification dropped the
fleet's activity count to zero, but the follow-up turn the CLI starts on its
own only reads as busy at its first message_start (seconds later on a large
context). Light mode released caffeinate in that gap, and a Mac idle past its
sleep timer went to sleep within ~5 s — mid-turn (seen 2026-09-18: slept 1 s
before the re-hold).

The release that follows a hold now waits LIGHT_RELEASE_GRACE_MS (60 s) and is
cancelled if activity comes back. Turning Caffeinate off still releases at
once. The set_awake driving moves to a testable useAwakeAssertion hook.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@Alex375
Alex375 merged commit 3bd17a5 into main Sep 18, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants