Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion .github/release-notes/v2.3.2.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
- Fixed `git_push` and the first push from `pr_create`. No changes to your Git settings are needed.
- File links can reveal files outside the active project after confirmation.
- Improved session recovery and made pending browser actions cancel when their tool call stops or times out.
- Updated the recovery notice and included the Unslop design skill in the source tree.
- Clarified the warning about unfinished work after a restart.
8 changes: 8 additions & 0 deletions .github/release-notes/v2.4.0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
# V2.4.0 - Watcher

- **Run → Monitor:** Watch a specific GitHub Actions run or a supported local MCP completion event. Results stay in Monitor unless you opt in to a short, tool-free reply in the original saved chat. Watches are local to the running desktop process and do not resume after a restart.
- **Desktop tray:** Keep Fate available after closing the window; quit from the tray to stop the app.
- **Work → Files:** Preview Word `.docx` paragraphs and headings and save notes for that document revision without editing the file.
- **Work → Changes:** Save a local note on changed lines and check GitHub PR status for the current commit. A previous result or note is marked stale when its revision changes. The review controls do not post, merge, or push.

See [Features](https://github.com/Master0fFate/fateUI/blob/v2.4.0/docs/features.md) and [MCP](https://github.com/Master0fFate/fateUI/blob/v2.4.0/docs/mcp.md) for setup and limits.
2 changes: 1 addition & 1 deletion PRODVER
Original file line number Diff line number Diff line change
@@ -1 +1 @@
2.3.2
2.4.0
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ Browse inside the workspace, select page elements, and attach browser annotation

### Review the work, not just the answer

Inspect file changes with Monaco diffs, browse Git history, and use the activity timeline to investigate tool actions. A separate manual terminal stays available for your own commands.
Inspect changes in Monaco, attach local notes to changed lines, and check GitHub PR status for the current commit. Preview Word documents and leave notes without modifying the source. Use Git history and the activity timeline to investigate changes.

[Files, Git, and activity →](docs/features.md)

Expand Down Expand Up @@ -208,6 +208,8 @@ Preserve existing behavior outside the requested scope.

Later `fate` launches reuse the running workspace. **File → New Window** opens another synced view. In the current V2 candidate, `--new-instance` selects a separate Chromium profile slot, but startup is refused while another core owns the same canonical Fate data root. Independent shared-data runtimes remain an unresolved ownership requirement. [Sessions and processes →](docs/sessions-and-processes.md) · [V2 candidate status →](docs/v2/current-status.md)

On Windows and macOS, closing the last Fate UI window hides it to the tray without stopping the app or reloading the window. Double-click the tray icon or choose **Open Fate UI** from its menu to restore it. On Linux, the last window minimizes so it remains accessible from the taskbar even if your desktop doesn't show tray icons. Desktops with tray support can also use their native tray activation or **Open Fate UI** from the tray menu; some shells require an extension to display StatusNotifierItem icons. Closing an extra window still closes that window. To stop the app, choose **Quit Fate UI**.

## Local-first, with explicit boundaries

Projects, session history, settings, and credentials are stored locally. **Prompts and selected context are sent to the AI provider you configure.** Browser pages, provider discovery, optional downloads, and other network-enabled features also use the network; local-first does not mean offline-only.
Expand Down
44 changes: 44 additions & 0 deletions THIRD_PARTY_NOTICES.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,50 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
```

## Word review

The Word preview uses `saxes` 6.0.0 and `xmlchars` 2.2.0 for XML. `saxes` and its upstream `sax` code carry the ISC License, reproduced below from the [saxes 6.0.0 source](https://github.com/lddubeau/saxes/blob/v6.0.0/LICENSE). `xmlchars` carries the MIT License from its published package. The ZIP dependencies `yauzl` 3.4.0 and `pend` 1.2.0 are MIT and retain their license files as installed dependencies.

```text
The ISC License

Copyright (c) Contributors
Copyright (c) Isaac Z. Schlueter and Contributors

Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
```

```text
Copyright Louis-Dominique Dubeau and contributors to xmlchars

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN
AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
```

## Bundled fonts

Fate UI bundles local Fontsource assets, including Roboto Flex (`@fontsource-variable/roboto-flex` 5.3.0) for the M3 Expressive skin and JetBrains Mono for Angelcore and code. These fonts are distributed under SIL OFL 1.1. Copyright notices and the complete license are included in [FONT_LICENSES.md](FONT_LICENSES.md), which accompanies packaged distributions. No Google brand font or remote font service is required.
Expand Down
Binary file added build/trayTemplate.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added build/trayTemplate@2x.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 2 additions & 0 deletions docs/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ The renderer has no Node.js, Electron, filesystem, credential, shell, or child-p
- The **preload** exposes only narrow, named, Zod-validated methods and events.
- The **renderer** is presentation-only and must never gain Node, Electron, filesystem, credential, shell, or child-process access.

Word review reads only bounded, project-confined `.docx` files in the main process and sends structured text, not document HTML, across IPC. Its paragraph notes are stored in the desktop data folder. Diff notes stay in this desktop profile; neither kind of note becomes an agent instruction. The desktop PR status query uses the authenticated `gh` executable outside the project, is gated to the trusted active checkout, and returns a bounded summary for an exact commit. It does not write to GitHub.

## Trust model

Every project — opened from the terminal or picked by hand — gets the same **Trust / Open without Pi / Cancel** choice. Project-local resources (for example `.pi/agents`, `.pi` themes) never bypass that decision. The manual terminal remains visually distinct from Pi-generated tool execution.
Expand Down
2 changes: 2 additions & 0 deletions docs/development.md
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,8 @@ The cross-platform GitHub Actions package matrix runs for pull requests, pushes
- Native hosted runners build, install or mount, and smoke-test Windows x64, macOS Apple Silicon and Intel, and Linux x64 packages: Windows NSIS, macOS DMG and PKG, Linux AppImage and DEB.
- The version in `package.json` and `PRODVER` must match. The release tag is `v<version>`, and `node scripts/release-artifacts.mjs metadata --field display-version` combines that version with the optional `package.json.releaseName` for the display title.

The current source version is `2.4.0` (Watcher).

1. Merge the version bump and `.github/release-notes/v<version>.md` into `main`.
2. Manually run **Cross-platform installers** on `main` with the promotion inputs empty. Confirm the run used the intended commit, all four native jobs passed, and `verified-release-installers` contains seven installers and `SHA256SUMS`. This artifact is retained for 14 days. This run does not publish anything.
3. Push the version tag pointing to that verified commit. Let the tag workflow build, verify, and publish the release with its notes. Do not create a GitHub draft or publish it separately: the tag workflow owns publication and refuses to overwrite an existing release for the tag.
Expand Down
12 changes: 12 additions & 0 deletions docs/features.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,14 @@ Rewind skips a file and reports why when its current content no longer matches t

In the Review Runway, a text diff shows one row per hunk above the Monaco view. **Keep** marks a hunk as reviewed. **Reject** reverse-applies only that hunk with `git apply --reverse`, refreshes the diff, and drafts a feedback message with the rejected hunk for the agent. Untracked files have no hunks; revert the whole file instead. The hunk header is checked before the revert so a stale list never reverts the wrong lines.

### Local diff notes

On the local desktop, open **Work → Changes** and select a changed text file. Choose **Note** on a hunk and pick a Before or After range, or select changed lines in Monaco and press **Ctrl+Alt+N** (**⌘+⌥+N** on macOS). **Save locally** keeps one note per file in this desktop profile. A note does not edit the file, stage changes, post a GitHub comment, or send anything to the agent. When a refresh shows a different commit or different diff contents, the note is marked **Stale** and stays at its original range. **Local notes** is also available when the file is no longer in the changes list.

## Pull requests

In **Work → Changes**, **Check PR** looks up the current commit on `github.com` through the signed-in GitHub CLI. This only works for a local branch whose commit matches the known `origin` tracking branch and an unambiguous PR in that repository; fork PRs are not supported here. The row summarizes up to 30 checks and labels partial results. It does not poll, fetch Git refs, post, push, or merge. When Fate sees a new HEAD, the previous result is marked **Stale** until you check again.

Full-access root sessions get `git_push`, `pr_create`, and `pr_status`. `git_push` pushes the current feature branch to `origin` with an upstream and refuses `main` and `master`. `pr_create` opens a GitHub pull request through the GitHub CLI and pushes first when the branch has no upstream. `pr_status` reports state, review decision, mergeability, every check, and the failed log tail of up to three failing workflow runs, so a "CI failed, fix it" prompt has the evidence in one call. The GitHub CLI must be installed and signed in; Fate never stores GitHub credentials.

## Context inspector
Expand Down Expand Up @@ -75,6 +81,12 @@ Agent Teams children do not get these tools. Use the embedded browser for pages

Status, history, commits, Monaco diffs, and project-confined file browsing without leaving the app. Worktrees are switchable; the working-tree diff and branch history are both reachable. Isolated session and agent worktrees are plain Git worktrees inside the project at `.fate/worktrees/`; that directory is added to `.git/info/exclude` and hidden from the file tree, so the parent checkout stays clean. The server profile keeps them under its data root instead.

### Word review

In the local desktop app, open a `.docx` in **Work → Files**. **Word review** previews body paragraphs and headings with basic bold, italic, and underline. It does not reproduce page layout or render tables, images, embedded objects, or active links. Word is not launched and the preview does not contact external resources. Preview files are limited to 16 MiB and 512 body paragraphs; oversized or unsupported documents show an explanation.

Use **Add note** beside a paragraph, then **Save note**. **Edit note** lets you revise it; clear the text and save to remove it. Notes live in Fate’s local data folder, not in the document or repository. They reappear when you reopen the same file revision. When the file changes, reload the preview; notes from the earlier revision are not moved to the new text.

### Branches

The composer shows a branch chip for repository projects. On an empty session it opens a picker: switch to a local or remote branch, or create a branch from the current one by typing its name. Branches checked out in another worktree are listed with a **worktree** tag and open that worktree. Picking a branch while the working tree has uncommitted changes opens it in a managed worktree and leaves the changes on the current branch. Each local branch has a delete button with a confirmation; deleting also removes its worktree, and is refused while a running session uses that worktree or when the branch is checked out in the primary worktree. Once the session has a message the branch is fixed for that session and the picker is read-only. The agent names, switches, and renames branches through the `git_branch` tool (list, switch, create, rename), which runs with hooks and unsafe protocols disabled. Listing works at every permission level; switching, creating, and renaming need Edit files or Full access. Status, changes, and history refresh after the tool completes.
Expand Down
19 changes: 19 additions & 0 deletions docs/mcp.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,3 +24,22 @@ A local server process has the current user's OS rights, not Fate UI's project f
For a full Pi Terminal switch: install Fate UI, open **Settings → MCP**, review **Switch from Pi Terminal**, and use **Import missing Pi providers and MCP servers** if there are provider entries or basic global MCP servers to move. Restart Fate after importing providers and reopen the project after changing MCP servers. Test each MCP server before removing Pi CLI; Fate does not install the server program or its Node/Python runtime. Pi sessions, user settings, global skills, prompts and extensions use the same `~/.pi/agent` directory after Pi CLI is uninstalled, so keep that directory and any needed Node/Python installation. Package dependencies must remain installed there. Existing advanced servers stay with a compatible global Pi MCP extension; inspect the reported conflicts and unsupported entries before uninstalling anything. Fate does not copy project-local executable extensions, and it cannot guarantee every third-party extension's terminal-only UI works in the desktop SDK. Do not claim a complete migration while these checks fail.\n\nThis initial bridge supports stdio and Streamable HTTP, tool discovery and tool calls. It does **not** implement OAuth, bearer-token management, SSE fallback, MCP prompts/resources, per-tool approvals, or per-project configuration. Servers needing these features require a separately installed, trusted Pi extension until Fate UI adds them. It creates and closes one connection per operation to avoid child processes leaking across project/session switches; some servers may start slowly. Large responses are truncated for model context.

Context Mode's current Pi extension also includes its own MCP bridge. Install it as a trusted global Pi package if you want its extension hooks; adding its server here is not necessary for the extension's own registered `ctx_*` tools. Do not configure both paths without a reason.

## Local Monitor watch connectors

A Monitor watch uses a separate, one-shot connection to a named, enabled **local stdio** server from Settings → MCP. It does not list or call tools, and an ordinary MCP tool server will not work unless it explicitly implements the watch protocol. The connector runs with your OS rights. Fate asks for native confirmation before enabling a new, changed, or previously disabled local command. Imported local commands stay disabled until approved. HTTP MCP servers are not supported for watches.

### Run the example

1. Install the repository dependencies with `pnpm install` and have Node.js installed locally.
2. Add and enable a stdio server named `watch-demo` in **Settings → MCP**. Set the command to your Node.js executable (use its absolute path if needed), and set the arguments to a JSON array with the absolute path to [`examples/mcp-monitor-watch.mjs`](../examples/mcp-monitor-watch.mjs). On Windows, use forward slashes in the argument path or escape backslashes in JSON.
3. In a trusted saved desktop chat, open **Run → Monitor** and start an MCP watch for connector `watch-demo`, event ID `example-job`, revision `demo-1`. The example sends `success` about one second after subscription. By default the result stays in Monitor. To also get a saved assistant update, check **Automatically reply in this chat when the watch completes** and enter a follow-up instruction. Automatic replies require a saved chat that is already loaded. When it is idle, its configured physical model receives only the completion facts and that instruction, with no tools or chat history. A completion does not reopen a closed chat. The update appears in the original chat without changing your selection. Extension-only models and command-backed provider credentials or headers are not supported for automatic replies. If an OAuth token needs refreshing, use the provider in a regular chat before relying on an automatic reply. This server provides no tools, so try it in Monitor rather than using **Test saved server**.

### Wire protocol (version 1)

- Advertise `"experimental": { "fate.monitorWatch": { "version": 1 } }` in the MCP initialize result's `capabilities`.
- Handle the `fate/watch/subscribe` JSON-RPC request with params `{"eventId":"example-job","revision":"demo-1"}` and acknowledge it with result `{}`. Reject unknown identities rather than subscribing to something else.
- Send a JSON-RPC notification (no `id`) with method `notifications/fate/watch` and params `{"eventId":"example-job","revision":"demo-1","result":"success"}`. The other terminal results are `failure`, `cancelled`, and `other`. Fate also requires the exact event ID and revision; unrelated notifications are ignored.
- Reserve stdout for newline-delimited MCP messages. The client ignores stderr, allows up to 10 seconds to initialize and subscribe, and accepts at most 64 KiB of stdout total. Fate closes the connection after one terminal result, on cancellation, or on failure. Stop connector work when stdin closes. Fate manages the connector process, not its descendants; do not use a launcher that leaves background processes behind.

GitHub Actions watches use a different adapter. They require an authenticated local `gh` CLI with access to the Actions run on `github.com`. Enter the literal `OWNER/REPO`, decimal run ID, and full commit SHA. Fate checks the returned repository, run ID and SHA before using a conclusion. Each lookup has a 10-second deadline and a 64 KiB output limit. No workflow is triggered, and enterprise hosts are not supported. Watches expire after one hour. Switching projects does not stop them, but explicitly closing the watched project or quitting Fate does. Watches do not resume on restart.
Loading
Loading