Clawdline 2.5.0

Clawdline 2.5.0

Watch published videos inside the conversation, follow the subagents working for your assistants, and manage more of your work without leaving Clawdline.

• Watch videos in place. Published MP4 links open a dedicated lightbox above the conversation. Playback starts while encrypted chunks arrive, with native playback controls, a reserved player area, loading feedback and reliable closing and reopening. Conversation cards select detailed preview frames from several parts of the movie. Links to another Session on the same paired machine use that video's source identity while preserving the conversation underneath.
• Follow subagents from Cloud. Session lists show current provider subagent counts. Open their activity views to see their own model and work; viewing the activity clears its phone indicator. Claude Code and Codex subagents retain their provider identities.
• Use a wider Board on desktop. Desktop columns fit the console and scroll horizontally while the phone layout stays familiar. Assignments follow the Agent language preference.
• Keep moving while actions finish. Common actions show their pending state, and Playbook starts show loading feedback. Console shortcuts have a discoverable cheat sheet. Phone terminal pasting opens its input before waiting for clipboard access, and scheduled history keeps its Close button available while scrolling.
• Let Agents maintain Playbooks and leave Notes. The command line can list, create, edit and delete saved Playbooks through the daemon's credential gate. Live Clawdline children can leave attention Notes for the person. Playbook keeps its English product name in the Traditional Chinese console.
• Keep assistant conversations connected. Managed Codex sends preserve their conversation history. Assistants started in Terminal can receive Session messages. Codex children with edit permission can stage and commit their changes and start with configurations containing a retired Codex setting. Gemini supports naming from its saved conversation, interrupting a turn, queuing the next message and answering native permission offers without cancelling the conversation.
• Recover without unnecessary interruptions. Sends can retry after execution verification recovers. Returning to the app rechecks a retained sign-in screen; temporary startup connection failures do not immediately become a sign-in request. Restart recovery offers can be dismissed from the Session list. Larger image messages pass Cloud envelope validation.
• Review an update before installing. The update flow shows the release changelog before confirmation. Session counts prioritize work needing your attention, All machines hides verified Dev builds ahead of the public release, and Cloud home-screen launches use the logo splash screen.

This release also makes screen capture, native role startup, quota and encrypted-carrier regression checks wait for their actual completion boundaries.

Clawdline 2.4.1

Clawdline 2.4.1

Completion notifications arrive after the final answer finishes, with fixes for Codex task networking and a lighter scheduled-run history.

• Read the answer when the phone buzzes. A Session delivery report records its receipt immediately and waits to notify you until a fresh observation shows that same conversation idle. Long answers, unreadable or retained state, and restart recovery cannot release the notification early. Concurrent recovery cannot send it twice.
• Codex tasks can reach the services they need. Non-interactive full-permission dispatch explicitly enables network access inside the workspace filesystem sandbox, including the local daemon. Other permission profiles keep their existing policies. Existing processes pick up new launch settings when resumed or relaunched.
• Open scheduled history in smaller batches. History starts with ten runs and reveals ten more with each press, including keyboard navigation. Stored history retention is unchanged.

Encrypted carrier read checks also wait for their asynchronous send to finish, making connection regression checks follow the real transmission boundary.

Clawdline 2.4.0

Clawdline 2.4.0

Gemini gains roles, shared Project memory and native workers, and its Session entry is available to everyone connected to a configured machine.

• Gemini for connected users. The ordinary Session chooser no longer hides Gemini behind administrator access. The machine owner still enables the personal-account integration and signs into the official Antigravity CLI with AI Credits off.
• Separate conversations in one Project. Two Gemini conversations can remain active in the same Project without sharing their messages or permission answers. Identical permission questions in different Sessions remain separate requests.
• Answer native tool permissions. The phone and desktop Session display the CLI's offered choices and return the selected answer to that request. A workspace refusal remains a refusal, rather than an approval prompt that cannot succeed.
• Keep the original role and memory. A Gemini conversation starts with its selected role, handbook, enabled skills, shared Project memory and language. Resuming preserves that original snapshot. Native tools identify their own Clawdline conversation instead of borrowing a parent assistant's identity.
• Gemini workers use the existing workflow. CLI dispatch can run a Gemini child through the existing role squad, claimed worktree, acceptance and result lifecycle. Native model and permission settings require acknowledgements. Closing a worker stops its exact process while retaining saved history.
• Completion notices keep their own receipts. A Gemini root can receive a worker's completion notice and acknowledge the task through Clawdline. A cancelled or limited turn is not counted as a completed observation, and an unrelated later success cannot mark that earlier notice read.
• Cloud terminals accept the current content key. Session and terminal access now use the same current-key and viewer-grant rules, fixing terminal entries that were refused while the corresponding Session remained readable.
• Connection delays keep the pairing. A delayed Cloud read no longer asks the person to pair the machine again. A confirmed pairing failure still receives its own recovery guidance.
• See the next scheduled agent. Schedule details show the agent assigned to the next run.

Gemini remains a machine-enabled personal-account preview using Antigravity's native ACP connection. It does not enable AI Credits, API-key fallbacks or paid APIs. This native process path supports macOS and Linux; native terminal attachment and turn-only cancellation are not provided.

Clawdline 2.3.0

Clawdline 2.3.0

An opt-in Gemini preview brings personal-account conversations, native model controls and saved history to the phone and desktop console.

• Gemini conversations. The preview uses the official Antigravity CLI's personal-account ACP connection to create a conversation, send a message and read its streaming reply through the existing Session interface. It requires the existing personal preview setup; AI Credits and API-key fallbacks are not enabled.
• History survives a restart. Saved Gemini conversations retain their identity and remain readable before the CLI reconnects. A new message resumes the same native conversation. An interrupted prompt is not automatically resent. Older native conversations can be found in the project's history chooser and imported explicitly.
• Read the whole conversation. Older structured pages stay in place while the newest reply updates. Repeated text in separate turns remains separate, and completed tools refresh their retained older page without dropping messages when a result grows.
• Models and reasoning effort are separate. Gemini Session Info presents the native offered base models and reasoning levels independently. Available native quota readings remain separate from conversation context.
• Less friction on the phone. The Gemini preview uses the same gradient mark across entry points, accepts input without a redundant availability preflight, and continues displaying the reply after the delivered message appears.
• A temporary terminal-listing failure keeps one Session. A returning terminal is reconciled with its original Session instead of appearing as a duplicate.
• Phone pairing follows the setup guide. The pairing QR view shows the same three steps as the guide, with one phone's progress kept together.

Gemini remains an opt-in personal-account preview. This release does not broaden its availability to other accounts or claim that the full Gemini integration is complete.

Clawdline 2.2.0

Clawdline 2.2.0

A setup guide in the Mac app walks you through connecting Cloud and pairing your browser and phone, and Cloud reads hold up better when several devices are open.

• Setup guide. A button beside the connection light in the Mac app counts what is set up: the Mac app, a browser and a phone. It opens a guide that signs this machine in, connects it, and pairs each device in turn. Any step can be skipped, and the finished screen takes you back to it. Choosing Keep it local leaves a quiet Local mark instead. Open it again from Help → Setup Guide….
• Pairing from a QR or link finishes at once. After you scan the machine's QR or open its pairing link, there is no fingerprint screen to compare; the pairing is already verified.
• Scan to pair. If a machine you can see online stops answering a device, for example after you removed that device on the machine, the notice offers Scan to pair instead of only Try again.
• Fewer false alarms. A read that fails for a moment, such as while the machine restarts or your phone wakes, no longer flashes a failure notice.
• Reads wait instead of failing. When several devices read the same machine at once, extra reads now wait their turn instead of being refused.
• Image drop frames stay visible over Session banners.
• A Secret Handoff Note finishes as soon as you submit the value.

Clawdline 2.1.3

Cloud setup now follows three steps: sign in, connect the app's machine, then pair a browser or phone.

• The macOS App opens Cloud sign-in in your default browser. Settings accept pasted pairing codes and show pairing results.
• Browser and phone setup regain a QR-code entry, with iPhone and Android instructions, expiry recovery and a pairing command that finds the installed CLI.
• When iTerm2 integration is off, sending shows a confirmation dialog. Cancel keeps the setting unchanged; enabling integration keeps the original message for you to review and send.
• Account quotas appear in a shared footer, with separate desktop and phone visibility settings. Sessions show reasoning effort beside model information.
• Mac downloads include a signed and notarized DMG. Installation and pairing guides are shorter and follow the setup order.

Cloud 設定依序完成三步：登入帳號、連接 App 所在機器，再配對瀏覽器或手機。

• Mac App 使用預設瀏覽器登入 Cloud；設定可貼入配對碼並顯示結果。
• 補回 QR Code 配對入口，加入 iPhone、Android、過期重試及尋找已安裝 CLI 的配對指令說明。
• iTerm2 整合關閉時，傳訊會顯示確認視窗；取消不改設定，開啟後保留原訊息供確認及傳送。
• 共用頁尾顯示帳號額度，可分別設定桌機與手機是否顯示；Session 的模型資訊也顯示推理強度。
• Mac 下載提供已簽章及公證的 DMG；安裝與配對指南已精簡並調整步驟順序。

Full Changelog: v2.1.2...v2.1.3

Clawdline 2.1.2

Clawdline 2.1.2

Cloud reads recover more reliably, and an interrupted refresh no longer covers your work with a pairing prompt.

• Existing paired browsers can keep reading over a direct connection without pairing again.
• A direct read refused by an older machine automatically tries the authenticated relay within the same timeout.
• Slow reads no longer make other reads wait behind one shared operation lock.
• A refresh that still fails appears in a small, dismissible status row. Your content and unsent drafts stay available, and a successful refresh clears the notice.

Clawdline 2.1.1

English

Clawdline 2.1.1 improves Cloud pairing and recovery.

• In the macOS App, pair its Cloud browser directly with the same machine after a native confirmation. No terminal or AI agent is needed for that handover.
• Browser pairing now includes a complete command to copy and run on the target machine. Instructions no longer point to a retired settings field.
• Cloud read errors offer both retry and pairing. A lost or expired browser offer can be renewed without deleting the device or signing out.

Signing in and pairing remain separate: this release keeps the machine's cryptographic verification and existing access permissions. A timeout can also have other causes; retry remains available. On iPhone, finish pairing in the same Safari tab or Home Screen app that you intend to use, because their keys are separate.

臺灣繁體中文

Clawdline 2.1.1 改善 Cloud 配對與讀取失敗後的恢復流程。

• macOS App 的內建 Cloud 瀏覽器可以在原生視窗確認後，直接與同一台機器配對，不必開終端機或啟動 AI Agent。
• 瀏覽器配對頁提供包含配對碼的完整指令，可直接複製到目標機器執行；不再指向已移除的設定欄位。
• Cloud 讀取失敗時，可以選擇重試或重新配對。配對碼失效後可重新產生，不必刪除裝置或登出。

登入與配對仍是兩個步驟：這次修改保留機器端的密碼學驗證與既有權限。逾時也可能有其他原因，因此仍提供重試。iPhone 的 Safari 與主畫面 App 各有自己的金鑰，請在實際要使用的同一個瀏覽器或 App 裡完成配對。

Clawdline 2.1.0

Clawdline 2.1.0 strengthens installation verification and remote-device permissions.

• The current installer verifies the signed manifest and archive before running downloaded code, using trusted local Python 3 and OpenSSL 3.
• Paired devices can have read-only access or permission to operate. Cloud browsers have separate persistent permissions.
• Revoking a Cloud device rotates the content key for future content. Remaining authorized devices can recover the new key through an authenticated exchange.
• Official macOS payloads are Developer ID signed and notarized. Archives include SPDX SBOMs and GitHub build-provenance attestations.
• Desktop image previews offer a direct download.

Cloud transcript content is encrypted on the machine before upload and decrypted by authorized endpoints. Endpoint access, connection metadata and trust in published software remain relevant security boundaries. See the security explanation and public agent review reports.

---

Clawdline 2.1.0 加強首次安裝驗證與遠端裝置權限。

• 現行安裝程式使用本機可信任的 Python 3 與 OpenSSL 3，在執行下載的程式前驗證簽署清單與安裝檔。
• 配對裝置可區分只讀與操作權限；每個 Cloud 瀏覽器都有獨立且持久的權限設定。
• 撤銷 Cloud 裝置後，未來內容會改用新金鑰；仍獲授權的裝置可透過經驗證的交換流程恢復讀取。
• 官方 macOS 程式已使用 Developer ID 簽署並送交 Apple 公證；安裝檔附有 SPDX SBOM 與 GitHub 建置來源證據。
• 桌面版圖片預覽提供直接下載。

對話內容會先在機器端加密才上傳 Cloud，由獲授權端解密。端點存取權限、連線中繼資料與發布程式的可信任程度仍是安全邊界。詳見安全性說明與公開 Agent 檢視報告。

Full Changelog: v2.0.0...v2.1.0

Clawdline 2.0.0

Clawdline 2.0.0

Clawdline 2.0 brings static HTML reports, more flexible schedules, clearer machine
controls, and smoother everyday navigation. It also retires the built-in
Cloudflare tunnel, so remote-access users should read the migration note below.

Remote-access migration

The clawdline tunnel command, /v1/tunnel API, and automatically generated
trycloudflare.com address have been removed. Existing tunnel settings are read
as off. Use Clawdline Cloud for paired remote access, or configure Tailscale Serve
for a direct connection over your tailnet. Review remote settings after upgrading;
old tunnel addresses will not be recreated. This removal is why this release is
2.0.0 rather than a 1.x feature release.

Existing Sessions and Projects remain in place. This release does not enable a
new remote-access method on your behalf.

Reports and schedules

• Open static HTML reports through the authenticated document viewer, including
  validated inline screenshots. Reports stay in an isolated preview and can open
  full screen. Phone document links retain their destination.
• Repeat schedules every chosen number of calendar days.
• Retained Cloud delivery receipts no longer participate in live queue sorting,
  avoiding repeated work as completed items accumulate while preserving receipts.

Everyday work

• Pairing leads with the action appropriate to the device you are using. Machine
  settings, connection details, names and access controls share a clearer layout.
• Session menus, the sidebar and disclosures open and close without losing their
  place. Loading screens show their layout while the first reading arrives.
• Codex history loads in pages and resumes the selected conversation. Queued work
  stays visible when a terminal changes state.
• Usage filters include configured Projects, background commands are separated
  from agent dispatch counts, and dispatched usage returns to its source Project.
• Project marks support SVG, and interface translations cover more controls and
  recovery states.
• Agents can withdraw their own Notes when attention is no longer needed.

Reliability and security

• Independent Cloud viewers retain their Session connection when another viewer
  connects, and each phone keeps its own notification subscription.
• Release staging rejects unsafe versions and archive links. Installation cannot
  write through a link outside the archive.
• Untrusted Markdown stays inert, and malformed CSS source maps cannot stall a
  console build.
• Closing an unreadable Session requires an explicit force-close decision.

The next round of Cloud entitlement-read optimization is not included in this
release. Local performance baselines do not establish a production user-capacity
limit.