Skip to content

Releases

FolioPier AI 0.3.1

Choose a tag to compare

@github-actions github-actions released this 12 Nov 18:37
8c4f3ff
  • Rename the product to FolioPier AI, with a new abstract mark, paper companion and updated desktop/mobile icons, workbench labels, notifications and document-share branding.
  • Make foliopier the primary command while retaining mydash as a compatible alias. Existing documents, configuration, service identities, browser state and Agent permissions remain in place. No manual data migration is needed.
  • Refresh the English/Chinese product introduction, screenshots, installation and connection guides. The repository moves in place to vanmiku/foliopier; old Git URLs continue through GitHub redirects.
  • New dedicated Tailscale nodes default to foliopier. Existing devices keep their current names and addresses; use the actual address printed by the installer.

mydash 0.3.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 23:40
  • Share published Markdown documents and selected attachments through a dedicated Tailscale Funnel reader. Visitors need only a browser, a link and its required 8-digit access code. Links expire after 24 hours by default, support up to 30 days, and can be extended, stopped or given a new code from the share manager.
  • Keep the published document's Markdown, tables, images, diagrams and file switching in the public reader. Add real PDF downloads using Chrome, Chromium or Edge on the hosting computer. HTML attachments use isolated, script-free previews.
  • Follow published document updates or share a fixed version. Newly referenced resources require owner approval before they become public. Visitors receive a version-update notice while keeping their unfinished comment drafts.
  • Let visitors leave private, file- and version-specific comments for the owner. Comments appear in share management and mydash feedback as external, untrusted input; they do not send instructions to an Agent.
  • Keep Agent conversations, internal feedback, approval answers and workbench APIs outside the public reader. Sharing uses a dedicated Funnel port and preserves the private workbench. Setup and management are opt-in, with visitor preview, expiry controls and access-code reset. Cleanup remains bound to the node that owns the public route.
  • Make every file tab reachable on narrow screens with arrow controls and a draggable position bar. Long labels fit the visible strip and retain their full filenames. The workbench and public reader use the same navigation.
  • Retry transient Windows LAN authorization lock conflicts within the existing deadline, preserving other devices' authorization and lock ownership.

After updating, refresh open pages. Open Settings → Internet document sharing (设置 → 互联网文档分享), complete Tailscale Funnel authorization, then choose Share on an article. The host must remain online for visitors to read shared content. Updating preserves existing data, network settings and Agent sending permissions. See the setup guide / 中文说明.

mydash 0.2.9

Choose a tag to compare

@github-actions github-actions released this 09 Nov 21:21
92b2e94
  • Opening a CSV or TSV raw link in a browser now shows a scrollable table, including on the isolated content port. Downloads, programmatic reads and byte-range requests retain the original file. The table-only preview has no scripts or workbench API access; existing access gates still apply.
  • Embedded CSV previews preserve the origin needed to include existing authorization cookies when downloading; scripts remain blocked by both CSP and the sandbox, and the content port remains isolated from the workbench API.
  • CSV parsing ignores delimiters inside quoted headings and cells, handles CR/CRLF rows and Excel separator hints, and supports UTF-16 BOM files alongside UTF-8 and GBK. Extra cells in ragged rows are retained and missing cells are padded instead of silently dropping columns.
  • Existing CSV files benefit after updating and refreshing the page; they do not need to be uploaded or published again. No data migration or permission changes are required.

mydash 0.2.8

Choose a tag to compare

@github-actions github-actions released this 06 Nov 17:27
89190ea
  • Press Enter to send an Agent message from an article sidebar or a standalone conversation; Shift+Enter inserts a new line. The input tooltip explains the shortcuts. Refresh an already open page after updating; no settings changes are required.
  • Confirming Chinese or other IME composition does not send the message. Held-key repeats, blank messages, unavailable connections and an in-progress submission do not create another delivery. Keyboard sending uses the existing draft, attachment, connection and retry-deduplication flow.

mydash 0.2.7

Choose a tag to compare

@github-actions github-actions released this 05 Nov 12:05
826167b
  • Answering native Codex questions while the original turn is active now uses the correct local steering protocol version and supplies the draft context required by the App, while preserving the original model and permissions. Synchronous question replies also use their correct protocol version. An unanswered question with a live original session and waiting process can be answered later.
  • Persist waiting-process heartbeats at a bounded frequency so the file-based Stop guard still recognizes long-running native questions; do not treat a live waiter as stale just because no other prompt changed.
  • Add a read-only “Reconnect Codex” action on pending native questions. It refreshes only the original session connection, can load that same original thread on the hosting Mac when necessary, keeps the current selection, and never submits an answer or retries an unconfirmed delivery. Preserve specific safe failure codes and show recovery messages inline instead of only in a short-lived toast.
  • Refresh a changed App owner before dispatching a question answer. Only discovery is repeated; the answer itself is sent at most once. Keep bounded failure-stage diagnostics without recording private conversation text.

mydash 0.2.6

Choose a tag to compare

@github-actions github-actions released this 04 Nov 23:26
afb29a8
  • Keep unanswered native asynchronous questions in the active Codex turn: guidance now waits for the answer before finishing, and a bounded Stop guard catches premature completion that would hide the App controls. First-message and plain-text-question reminders also prefer the asynchronous native tool instead of falling back directly to CLI.
  • Codex choice questions now prefer the native question tools, including the desktop asynchronous tool in Default mode. The question stays visible in Codex while mydash shows a mirror; the CLI fallback is used only when neither native tool is available.
  • New installations default to asking in both places. Supported desktop connections can submit an answer to the exact original question; existing explicit app-only and mydash-first settings are preserved. Command approvals keep their existing behavior and permissions.
  • Native answer delivery checks the project, question, and current owner. Duplicate submissions and uncertain delivery are held for confirmation, and a disconnected connection keeps the user's selection. Multi-question mirrors close after all original questions have been answered.
  • Existing installations refresh managed agent guidance on update. User-maintained instructions that explicitly require mydash ask may need to be updated to prefer the native asynchronous tool too.

mydash 0.2.5

Choose a tag to compare

@github-actions github-actions released this 04 Nov 21:19
  • Redirect HTTP Tailnet pages to HTTPS only after native certificate verification and installation-identity checks pass for both the workbench and isolated content origin. Readiness expires and is invalidated by address changes; background checks are shared and bounded so pages remain usable while HTTPS is unavailable. Settings show the actual network address, connection state and an automatic-redirect switch restricted to local/trusted Tailnet access. Access-mode changes discard inherited HTTPS addresses.

  • Connect to already loaded original sessions in the newer shared Codex app-server daemon over its private Unix WebSocket, including its protected socket symlink. Verify the project, thread and direct-input capability before enabling send; preserve the original model and permissions. Keep the desktop broker fallback for older installations and never switch transports to retry an unconfirmed submission. Add pinned ws for the native WebSocket framing/handshake (no framework or new network listener).

  • Classify explicit Codex protocol-version/missing-handler errors as incompatible connections. Add a read-only support probe, compatible with existing 0.2.4 code, that reports App versions, socket checks and per-RPC codes without exposing conversations or starting delivery workers.

  • Doctor verifies both Serve forwards for standalone Tailscale nodes and checks the installation identity behind network addresses. A running node, another mydash instance or an unrelated HTTP 200 response no longer hides a broken network setup. The installation guide explains actual addresses, name collisions and MagicDNS prerequisites.

  • Completed, cancelled and stopped delivery notices disappear after five seconds; old success notices are not replayed. Each notice can be dismissed without cancelling the message or Agent work. Hidden pending statuses remain accessible, and new errors or confirmation requests can surface again. Article and standalone conversations share this behavior.

  • Show saved Codex messages immediately while the native App connection is discovered in the background. Only the selected, visible conversation is opened on the hosting Mac; viewing Contents or closing the mobile panel does not wake it.

  • With web messaging enabled on macOS, automatically open an existing original Codex thread through its registered App link. No dummy message, separate executor or permission changes are used. Connection attempts are deduplicated, bounded and rate limited; GUI login and connection failures retain drafts and provide a retry.

  • Accept first messages into the durable Codex queue while connecting, with cancellation, retry deduplication, permission revocation checks and the existing 30-minute expiry. Ordinary LAN browsers remain view-only and cannot wake the App. Settings explain the automatic-opening behavior; other platforms retain their existing connection methods.

mydash 0.2.4

Choose a tag to compare

@github-actions github-actions released this 04 Nov 17:09
9de8875
  • Discover resumed Codex rollout files with continuation ID suffixes, resolve duplicate files to the newest validated transcript and look up known threads beyond incremental indexing budgets. Active projects no longer fall back to stale copies or the wrong older conversation.
  • Locate background Codex App owners through read-only model-settings routing before verifying the exact owner and input capability. Allow the native broker to return its no-owner result before timing out, distinguish an unconnected conversation from a nonresponsive App, and provide a retry action that keeps the draft.

mydash 0.2.3

Choose a tag to compare

@github-actions github-actions released this 04 Nov 00:17
2a85077
  • Keep the selected conversation title and automatic/manual target mode visible beside each article. Replace the native select with a searchable, keyboard-accessible conversation picker that shows working/idle/unknown states, latest-project markers, update times, recent message previews, connection sources and short IDs. Opening the picker does not move messages; drafts remain attached to their original target.

mydash 0.2.2

Choose a tag to compare

@github-actions github-actions released this 03 Nov 23:42
d9dfe7b
  • Users with conversation viewing off see a dismissible, once-per-browser introduction. Its action opens the exact Terminal sessions settings section; viewing and sending remain independent opt-in choices. The introduction can be replayed in Settings.

  • Project identity checks read worktree metadata without spawning Git on each request, and small Codex updates retain unchanged history instead of copying it. Conversation polling pauses while reading contents or when the mobile panel is closed.

  • Connect long Codex App conversations with snapshots above 32 MiB. Receive fragmented frames with linear copying, retain a 64 MiB frame bound, and explain oversized histories instead of a generic timeout.

  • Use live App turn activity when choosing the current project conversation, so stale transcript timestamps do not keep an older thread selected.