|
|
|
@@ -4,6 +4,29 @@ All notable changes to this project will be documented in this file.
|
|
|
|
|
|
|
|
|
|
## [Unreleased]
|
|
|
|
|
|
|
|
|
|
## [1.16.0] - 2026-07-13
|
|
|
|
|
|
|
|
|
|
- **Session goals:** arm the new target button in the composer and your next prompt becomes a [goal](https://docs.openchamber.dev/session-goals/) — the session keeps working toward it on its own, with an independent small-model audit checking each finished turn, until the objective is verifiably complete, blocked, or over its optional token budget. The loop runs on the server, so it continues with the app closed and survives restarts. A goal strip above the composer shows progress with pause/resume; goals can also start from the plan-implement dialog, from scheduled tasks ("Run as goal"), or with the new "Craft a Goal" starter and `/craft-goal` command. While a goal runs, per-turn "ready" notifications are replaced by a single notification when it settles.
|
|
|
|
|
- **Usage:** OpenCode Go usage tracking is here, and Codex quota windows now show the correct reset times.
|
|
|
|
|
- **Remote access:** connecting over the relay got much faster — the app no longer waits for a stale local address to time out before trying the relay (previously up to ~20 seconds on a phone away from home). When your computer gets a new local IP, paired devices now learn the new address over the relay and quietly move back to the local network on their own — no re-pairing. The phone's launch screen shows which device it is connecting to.
|
|
|
|
|
- Remote access: running several OpenChamber instances on the same machine no longer makes paired devices land on a random one of them — only one process per machine serves the relay now. This was behind intermittent "Unable to reach server" errors on paired phones.
|
|
|
|
|
- Permissions: per-session auto-accept now lives on the server — sessions keep auto-accepting tool calls while the app is closed and after a server restart, subagent sessions inherit the setting, and it can be enabled on a draft before the first message (thanks to @bashrusakh for the draft fix).
|
|
|
|
|
- Chat: subagent sessions can now be prompted directly — open a subagent from the context panel and send it follow-up messages (off by default, available in settings).
|
|
|
|
|
- Chat: queued messages now send when the session is already idle instead of waiting forever in some cases, pending agent questions stay answerable after a server restart, and session renames no longer flicker back to the old title (thanks to @bashrusakh).
|
|
|
|
|
- Files: the file viewer has a markdown preview toggle (thanks to @greghaynes).
|
|
|
|
|
- Sidebar: projects can be sorted by different modes with a direction toggle, pinned sessions survive refreshes, and the file tree stays expanded while it refreshes (thanks to @bashrusakh).
|
|
|
|
|
- Command palette: projects are included in the fuzzy search alongside sessions and files (thanks to @bashrusakh).
|
|
|
|
|
- Settings: chat visual settings are grouped into labeled sections, and a new editor font size setting for the code editor (thanks to @bashrusakh).
|
|
|
|
|
- GitHub: PR and issue context now resolves against the source repository in fork workflows (thanks to @bashrusakh).
|
|
|
|
|
- Agents: saving agent settings from the UI no longer drops custom YAML frontmatter fields (thanks to @bashrusakh).
|
|
|
|
|
- Notifications: session errors and subagent completions now notify reliably across desktop, web, and mobile.
|
|
|
|
|
- Editor: "Open in" now recognizes VS Code Insiders.
|
|
|
|
|
- Windows: paths no longer mismatch on drive letter casing, which could split one project into duplicates (thanks to @bashrusakh).
|
|
|
|
|
- Mobile: the sessions sidebar opens instantly instead of taking many seconds on some devices (thanks to @tomzx).
|
|
|
|
|
- Mobile: renaming a saved instance no longer breaks its connection — the stored access token was getting lost on edit.
|
|
|
|
|
- Mobile: on Android 15 the app no longer draws under the status bar.
|
|
|
|
|
- Security: requests that spoof local host headers to look like same-machine traffic are rejected.
|
|
|
|
|
|
|
|
|
|
## [1.15.0] - 2026-07-10
|
|
|
|
|
|
|
|
|
|
- **Remote access:** a new [private relay](https://docs.openchamber.dev/private-relay/) lets you reach your instance from anywhere — no open ports and no third-party tunnel, over an end-to-end-encrypted tunnel. It turns on by itself when you pair a device over it and turns off once no paired device uses it (thanks to @yulia-ivashko).
|
|
|
|
|
Bohdan Triapitsyn