GIT AI · release notes

What changed in each version.

Newest first. The app updates itself; each version's notes also show in the app after it updates.

0.4.39

  • Make a key at once from your phone: confirm it with your passkey and the key is made without waiting for Allow on a Mac. A key with rights that run code still waits for Allow, and every key made this way shows a notice with Revoke.
  • A run goes in stages: CI first, then the gates a project turned on, so a red CI stops before the longer gates start.
  • Only the Rust crates a change touches are checked when a project runs just what changed.
  • Make a Key explains each right: an (i) beside "What it may do" says what a key with that right can do.

0.4.38

  • Macs work as one cluster: a Mac joins your cluster with one passkey, and you can keep a Mac out of it.
  • Pair once: after you pair your devices with one Mac, they work on every Mac of your cluster.
  • A pull request is checked merged with main, and its status goes on the pull request's own commit.
  • Build and test tools get a fair share of the Mac's cores, so two jobs at once no longer starve each other.
  • Settings has a Devices tab that lists and removes a Mac's browsers and apps, and a Secrets tab that lists secret names and sets a value through the Mac.
  • An agent with a key made on the controller connects through the agents' door.
  • Linux jobs: a project can push container images to the registries its owner allowed for it, and in Python jobs uv takes the image's Python version and waits longer for cache locks.

0.4.37

18 November 2026
  • Great_git's own Linux VM (for a Mac moved to it with gg setup --linux-engine own): Linux jobs run in a VM that Great_git prepares by itself in the background, starts again when it stops and restarts when its engine stops answering. A job that comes while the VM gets ready waits with "Getting Linux jobs ready on this Mac" instead of failing. OrbStack, colima or Docker Desktop on that Mac are never used for jobs. A Mac that is not moved keeps its current engine.
  • gg doctor says which engine runs Linux jobs, and whether Spotlight skips the folders jobs write.
  • Android jobs never write into the Mac's own SDK: when it lacks a package the job needs, the job uses Great_git's own SDK under ~/.great-git/tools/android-sdk.
  • A pull request's job is rerun on another Mac when its Mac is lost, instead of failing after 15 minutes. Push and release runs are not rerun unless the workflow asks for it with GG_FLEET_REPLAY: "1".
  • Home on the controller shows Running now: every run that goes or waits on every Mac, each a link to its run page.

0.4.36

18 November 2026
  • Docker inside a Linux job, for the projects you choose: steps that run docker build or docker run get this Mac's Docker engine when you list the project with gg setup --docker-socket <project> and the job asks with GG_LINUX_DOCKER: socket. Projects you did not list, and pull requests from forks, never get it.
  • Containers such a job starts see its files: its workspace and temporary folders are this Mac's folders at the same paths, so docker run -v "$PWD:$PWD" works as it did before 0.4.34.
  • API Keys tab with Edit… per key: change a key's name, rights or projects without making a new one. Taking something away applies at once; giving more waits for Allow on the Mac.
  • A key's rights one by one: Make a Key… and Edit… offer Read only, Run, Assistant or Custom, with each right listed under "Advanced", including running workflow text, dispatching and own branches, for any project. Allow on the Mac names each right added.
  • Two checkouts of one repository share their Linux job caches: a clone in another folder no longer starts with empty caches and its own set of volumes.

After updating: run gg setup --docker-socket <project> and restart

Great_git for each project whose jobs need Docker.

0.4.35

18 November 2026
  • Linux container jobs see their checkout again: 0.4.34 nested the workspace volume inside the shared job folder, so steps after actions/checkout found an empty workspace. Only the job's steps/ folder is shared now, and a volume that is not mounted fails the job instead of clearing the checkout.
  • uv projects in Linux job containers use uv's own Python, and an AI agent no longer makes an API key in this Mac's own state.
  • Add a Project is one sheet: folder, repository and a sealed token at once, with one Allow on the Mac.
  • A refused token says what GitHub answered: the HTTP status and GitHub's message, the rights it asks for on a 403, and on a 401 with text that is not shaped like a token, its length and whether a saved password was filled in. A token that is not kept is logged in ggd.log.
  • The agents' door is open: AI agents reach a project through agents.git.greatcto.systems, and the main Mac publishes the project ids that door needs.
  • Insights show total run time and the median and 95th percentile run duration, in the report and in gg insights.

0.4.34

17 November 2026
  • Passkey or authenticator code at every controller sign-in, with hints when the passkey is on a phone or in a password manager, and a choice in Profile of which way is asked first.
  • Make Main Mac… beside each Mac on Home, and each Mac drawn as its own card with CPU, Memory and Disk stacked.
  • Every run says whose it is and why: the project, who started it and a one-line note, in gg status and on the run page.
  • Linux container jobs get their own workspace volume, so installs such as npm ci no longer fail with "permission denied" on colima.
  • Container tools unpack outside the job's temporary folder, and the Maestro check skips _helper.yaml files next to the flows.
  • Token fields are left alone by password managers, and Edit names the three rights a GitHub token needs to post checks.
  • A controller restart no longer turns a Mac's Remote Control off.

0.4.33

17 November 2026
  • Invite a person by email to chosen projects of a Mac: the People tab of a Mac's Settings sends the invitation, shows who has access and to what, and lets you confirm a join by comparing the device's words.
  • Change, narrow or remove access: narrowing takes effect at the person's next request; giving more asks for your passkey; removing someone unpairs their browsers and revokes the agent keys they made.
  • The invited person sees only what was shared: "Shared with you by" in the menu, their access in words on each project, and "This is not shared with you" anywhere else.
  • Your bell says when someone wants to join, with a link to confirm on that Mac.

0.4.32

17 November 2026
  • Add a Browser… is in the menu: one click opens this Mac's page in your default browser and pairs it; Copy Link pairs another computer, and a phone scans the code. The browser you sign in with when Great_git starts is paired in the same step.
  • gg pair prints the same one-time link and this Mac's words on a Mac with no screen.
  • The web says "not paired" before you press anything: a browser without a key for a Mac sees a chip and a banner on that Mac's pages, change buttons wait until it is paired, and Pair This Browser… shows both ways to pair (one click on the Mac, or your passkey).
  • Gates of a Mac on the web: QA, Security and Documentation verdicts of each project's main branch, read only.
  • New Project waits while the Mac still has to allow a browser that signed in with a passkey only, instead of failing.
  • Remove says why the Mac refused, instead of "not reachable".

0.4.31

17 November 2026
  • Add a project from the web: New Project picks the repository and the Mac it runs on, and each project has its own page with its last run and its API keys, which you can make and revoke there.
  • Choose the main Mac from Your Macs, instead of joining Macs by hand on each one; and one menu for a Mac (Overview, Runs, Tests, Settings under one header), also on the phone.
  • Confirm a passkey made in a browser with Touch ID on the Mac before it can be used, and see and revoke a Mac's keys on the web.
  • Safer updates: the app carries a spare update key and a separate key for the minimum version, so a lost key can be replaced and a bad version retired. 0.4.30 had neither.
  • Sign-in always asks which Google or GitHub account to use.
  • Deleting Great_git.app stops its service and removes it from the login items, so the Mac no longer shows as online.
  • Linux jobs start sooner: the Linux image is downloaded in the background before the first one, and pull request runs in a container compare against the right main branch.

0.4.30

16 November 2026
  • Linux builds in a container are fast and no longer killed: a job gets a share of the Mac's cores, and it can use free memory beyond what it reserved, up to what CI may use on this Mac. In 0.4.29 big Rust builds ran out of memory; that version was withdrawn.
  • Give a project its own GitHub or GitLab access token in the project's Edit sheet. The token is sealed to the Mac that uses it.
  • Your account is one Profile item in the menu of the cabinet, and under More on the phone.
  • A job's own limits still win: CPU and memory options in a job's options: are used as written.

0.4.29

16 November 2026
  • Linux jobs in a container are fast again: a job gets a share of the Mac's cores instead of a fixed cap, so when the Mac is idle a build uses all of them. Memory stays limited to what the job reserves.
  • A job's own CPU limit still wins: --cpus, --cpu-shares or --cpuset-cpus in a job's options: are used as written.
  • A ready-made Linux image for Great_git's own CI, with Chromium's libraries, zig and cargo-zigbuild, so a run no longer installs them again (deploy/ci-image/build.sh, then gg setup --linux-image).

0.4.28

16 November 2026
  • A new look for the cabinet and the dashboard: the Inter typeface, near-black buttons and links, rounded pill buttons, quiet outlines and small status chips. Running is blue and a failed run stands out.
  • On a narrow screen the account stays in the menu: the cabinet's header no longer hides it between 600 and 959 px.
  • Backups are checked in container jobs too: the backup restore check gets its tools in a Great_git container job.

0.4.27

16 November 2026
  • Linux jobs in a container finish cleanly: a step that leaves processes behind no longer keeps the job waiting, and a compiled build is kept between runs, so the next run is faster.
  • Allow a change on this Mac itself when the Mac is in strict mode, and update it from the cabinet without pairing a browser first.
  • A new first run, menu bar menu and About window in the app, with plainer notifications ("A new browser was added").
  • Plainer words in the cabinet and the dashboard, the Mac page in one column, and a run page that fits a phone's width.
  • Invitations by email carry a join code the owner checks before someone joins.
  • Macs in one account share warm caches: a new Mac takes what the others already built.

0.4.26

15 November 2026
  • A Linux job can drive an Android emulator on this Mac: a job that runs in a container leases an emulator with great-git/android-device.
  • The job gets adb, Java and Maestro in its container, and they see only the emulator it leased, nothing else on the Mac.
  • The iOS simulator step (great-git/maestro with platform: ios) runs on this Mac through Great_git; the app it tests must be built before that step.

0.4.25

15 November 2026

This build replaces 0.4.24, which no Mac could update to: it carried a

build number lower than the builds already installed. It has everything

0.4.24 has, and:

  • Updates reach your Mac again: every build now carries a build number higher than the one before, and a build that would not is refused before it is published.
  • Linux jobs run in a container on Docker, not on the Mac itself, and get the tools their repository needs inside it: Node.js, pnpm, Yarn, Bun, Rust, Go, Java, uv, Python, Flutter, Caddy, Hurl and the PostgreSQL client. Every download is checked against a known checksum.
  • Name a tool your files do not show with GG_NEEDS in a job's env, and make a project strict with gg project tools NAME --strict on: a job then fails when a tool it needs cannot be provided.
  • Home uses the whole width of the window: every Mac's load in a table, and a bell that collects what needs you.
  • Android emulators are created with the Java Great_git already has, and restarting the service takes over a daemon you started by hand.
  • A Mac you set aside for assistants comes back as yours only when you reinstate it, and a damaged store stops the daemon instead of letting it carry on with keys it could not check.

After updating: Linux jobs need Docker (OrbStack or Docker Desktop)

running. To keep running them on the Mac itself, run

gg setup --linux-jobs host. What 0.4.24 asks of you applies here too:

an agent key that covers several projects stops working, so make one

key per project; in a fleet, update the leading Mac first.

0.4.24

15 November 2026

This build replaces 0.4.23, whose Mac app was never published.

  • Invite people to your Macs by email, with a role, and they sign in from a window of their own on the invitation page. People you invite reach your Mac only end to end encrypted.
  • In a fleet, you choose which Macs run your AI assistants' branches, so the Macs that hold your secrets don't run them; the files a step uses are private to you and removed when the step ends.
  • An agent key works on the one project it was made for, and a key you revoke stops working everywhere at once.
  • Report a Mac as lost: it is refused for good, and you are told what to change.
  • Updates are signed by two keys and never go backwards: a Mac refuses an update signed with a retired key or older than one it already has.
  • Simulator runtimes, Android images, Git and the Command Line Tools install on demand, without a terminal, and a new project can carry its own access token; you are told 14, 3 and 1 day before it runs out.
  • Short jobs keep their share of the Mac, and projects take turns fairly when several want it at once.

After updating: an agent key that covers several projects, or every

project, stops working; make one key per project with gg remote connect

--project <name> --name <name>. Someone you invite as a Manager for a

list of projects can't add new projects yet. In a fleet, update the

leading Mac first: the other Macs wait for it before they run jobs. This

is the version the site now asks your Macs for.

0.4.23

15 November 2026
  • Your passkey confirms the changes that matter, such as making an agent key, and it can add a new browser on its own. The Mac checks the passkey itself, not the service. The first passkey you add is confirmed on the Mac.
  • Every change to a Mac through the Remote Control service needs a browser paired with that Mac, and a request that was held back or replayed is refused.
  • Browsers check your Mac's own key, now shown as eight words, and what an agent key carries travels end to end encrypted, so the service never sees it. You can set a Mac to accept only encrypted requests, reads included, for every account it lets in.
  • Projects can live on GitLab (gitlab.com or your own GitLab over https), and every project keeps a permanent id when you rename it.
  • A project's tools install as soon as you add it, so its first run does not wait for downloads. pnpm, Yarn, Bun, Go and Ruby are new.
  • Home shows what needs you, every Mac with its level and load, and your projects with their last run. On a Mac's page you choose how much of it CI may use: Minimum, Medium or High.
  • Each commit gets a status per gate on GitHub (tests, security, documentation, builds). They report only, and block nothing.

After updating: a browser you added before shows your Mac's key as eight

words; compare them once with the words in the Mac app when it asks. To

use a passkey, add it in the browser, then confirm it in the Mac app.

"Only encrypted requests" stays off until you turn it on on the Mac.

0.4.22

  • Removing a project from Your Macs takes effect at once. No Allow on the Mac and no 15-minute wait: Great_git stops using the project, and its folder and files stay on the Mac as they are.
  • Cancel Request on Your Macs works. A request nobody answered no longer blocks adding, changing or removing projects until it runs out.
  • A changed setting from the browser needs your paired device's signature for every right that can run or change something, not only for Operator.
  • The Mac talks to the service only over TLS 1.3, trusting only the certificate roots the service uses.
  • A job can run its steps in a Linux container with container: in the workflow.
  • Files a run uploads are kept with their commit, their job and a SHA-256 checksum, so a build can be traced to the run that made it.
  • Download the app always opens the newest build.

After updating: nothing to do.

0.4.21

  • You manage your own Mac from the browser from the start. When you allow your own account in the app, "View, run and manage" is chosen, and Settings in the dashboard opens Settings of this Mac instead of a dead end.
  • A project knows its folder and its GitHub repository. Change them or remove the project from Your Macs; removing only takes away the browser's access, nothing on the Mac is deleted.
  • Update on Your Macs updates the Mac by itself, without anyone at the Mac.
  • Limit how many runs of one project go at once on a Mac.
  • The run page shows the step log on top, taller, with a Copy log button.
  • Clearer results: a test that skipped itself is "Skipped", a skipped job names the job that failed, and a key for the whole Mac also sees runs started outside any project.
  • Variables you set for this Mac reach every job.

After updating: nothing to do.

0.4.20

  • Great_git installs the tools a job needs by itself. Java, the Android SDK, Node, Rust, Flutter, Maestro and uv are downloaded for your user, without an administrator password, when a workflow asks for them.
  • Your Macs are cards, with a page for each Mac. It shows the Mac's hardware and load, also while it is offline, and lets you stop, start, restart or update Great_git there; a Mac's settings can be changed from the browser and are allowed on the Mac.
  • The menu and Runs say why a job waits and how long it will take, and a run can be moved to the front of the queue.
  • The app says when a newer version exists, in the menu, in Preferences and on your phone.
  • More GitHub workflows run as they are. Steps Great_git cannot run no longer stop the whole job before it starts, values like the workspace folder are filled in when the job starts, Docker is started when a job needs it, and astral-sh/setup-uv works.
  • Insights shows runs by day and tests that newly became flaky.

After updating: the first job that needs Java or Android may take a few

minutes longer while Great_git downloads them.

0.4.19

  • The app asks you to sign in when it starts. A window with one button, "Sign In with Google or GitHub…", opens the sign-in page in your browser and then says who is signed in. The same browser can open this Mac's dashboard right away.
  • After signing in, the browser ends on your Macs at the service, not on a page at this Mac's own address.
  • Signed in means connected. There is no "Turn On" for reaching this Mac from other devices any more, and no Pause; Sign Out is in Preferences, under Account.
  • The app looks like the dashboard. The menu, Preferences and the question "Allow … to open this Mac?" use the same cards, colours and words for a state as the pages in your browser.
  • The menu shows who is signed in and opens Overview, Runs and Tests with one click each.
  • Settings pages no longer load inside a window. Projects, Phone & Web, This Mac and AI Assistants open in your browser, like the rest of the dashboard.

After updating: the sign-in window comes up once. Until you sign in, the

app's other windows wait; your checks keep running in the background.

0.4.18

  • The dashboard opens only through app.git.greatcto.systems. Open Dashboard, a run's log, All Runs and the links in Preferences and in the Guide all open this Mac's page at the service.
  • A Mac that is not in an account yet opens the service's first page, where you sign in with Google or GitHub and add this Mac.
  • The app no longer opens the page at 127.0.0.1, and no longer asks this Mac for a one-time link to it.

Not in this build: the sign-in button in the app and the app's new look

are still to come; the settings panes inside the app's windows still

show this Mac's own page.

0.4.17

  • The app looks the way it was approved: one small Preferences window, the menu bar item and its menu, the Guide and See on My Phone.
  • Remote Control from the app. Turn it on in the menu or in Preferences: your browser opens git.greatcto.systems, you sign in with Google or GitHub and choose Add this Mac, then answer on the Mac who may do what. Sign Out of This Mac takes it out again.
  • Turning Remote Control on works with the address the app ships with. The app called the public page's address, which answers with a redirect, so adding this Mac failed; it now calls the service itself.
  • Banners say what failed and go away by themselves when it is fixed.
  • The service's pages show each Mac's state, let you delete your account, and say what happened when signing in fails.

Not in this build: Open Dashboard still opens this Mac's own dashboard

in the browser, not the page at git.greatcto.systems.

0.4.16

  • One run per commit. A commit that already has a run is not run again, and the runs of a closed pull request are cancelled, so the queue is not filled with work nobody is waiting for.
  • The dashboard uses the window it gets, wide or narrow.
  • Remote Control, when it is off, stays off: a request that was already on its way is not carried out.
  • The phone link counts only what came after its code, and goes by address only when the Mac's certificate names that address.

After updating: the app restarts Great_git's background service once, so

start it when nothing is running.

0.4.15

  • CI no longer waits for the rest of the Mac. On a Mac set up as dedicated, runs start as soon as there is room in the cores and memory you gave CI, whatever else is running: up to three big builds at once instead of one at a time. On a Mac you also work on, nothing changes. gg setup --when-busy first or yield chooses, and gg doctor shows which one is on.
  • The build you are waiting for starts first. In a run with several jobs, the one that builds the app goes before the tests next to it.
  • Only the build, when that is all you need. gg run .github/workflows/macos-app.yml --event workflow_dispatch --job app runs that one job, like building by hand.
  • The app is ready sooner. Its disk image can be downloaded as soon as it is built and checked; the remaining tests go on after that.

After updating: the app restarts Great_git's background service once, so

start it when nothing is running.

0.4.14

  • The hosted pages in the new design. Your Macs, Browsers and Your Data sit under one menu. (This note first also named a new menu, a Preferences window, Remote Control and banners in the app: they were not in this build and come in a later one.)
  • CI uses the Mac you give it. Choose how much of the Mac CI may take (Low, Medium, High, or gg setup --cpu-cores 8 --ram-gb 20). Up to three big builds run side by side, and the Mac counts as busy only when other apps load it, not when CI does.
  • Faster runs. Tests run in parallel, a change runs only the checks for what it touches, and jobs share Rust and browser downloads.
  • Emulators and simulators start only when a job needs one, and gg devices lists them while they are off.
  • The app can update itself. Check for Updates… shows what is new and installs it with one click, only builds signed by us, and never over running steps: a ready update waits until every run has ended.
  • Less disk. A run's work folder is deleted as soon as the run ends.

After updating: the app restarts Great_git's background service once, so

start it when nothing is running. A build you made yourself, without an

update address, has no Check for Updates….

0.4.13

  • Phone tests on your own emulator and simulator. Name an Android emulator or an iPhone simulator in setup and Great_git keeps it running for your tests, and makes it from an installed system image or runtime when it is missing.
  • A check on GitHub that runs on your Mac. A small Linux job can hand a pull request's checks to your Mac and wait for the result. The release now carries gg for Linux for that job, with a ready example.
  • After the Mac sleeps or Great_git restarts, GitHub shows why a check is still waiting and how many jobs are left.
  • The Flutter version your project pins is used when it is installed with fvm.
  • Fewer surprises while jobs wait. Running emulators count toward the Mac's memory before a job starts, Gradle builds wait their turn, and runs that share a concurrency group queue up as they do on GitHub.
  • Easier to read a failure. Your own test scripts' results show up per test when the job uploads a JUnit file, a failed job shows its failed step and the end of its log in the summary, and a job's log can be copied with one button.
  • The phone link and AI assistants hold up better: the phone opens the Mac by its address, and an assistant you approved renews its own access instead of asking again.

0.4.10

  • A key for Claude Code or Codex, in one step. Settings has a page AI assistants with one button, New Key. Say who it is for and which projects, and the key is there to copy.
  • One thing to paste, instead of four steps. Under the key is a block for the Terminal of the computer where the assistant runs. It checks that it is talking to your Mac, saves the key in a file only you can read, and connects the assistant.
  • A sentence to give the assistant afterwards, about a project of yours: run CI on my branch and tell me what failed.
  • The page says when it worked: "Connected" appears by itself at the assistant's first call.
  • The same page on your phone, for a device that may manage this Mac. A key that may start a release is made only at the Mac itself.
  • Each key shows its projects, when it was last used and how many days it has left, with Remove next to it.

After updating: assistants you connected before keep working. The key is

no longer written into ~/.zprofile; an old line export

GREAT_GIT_TOKEN=... there can stay or be deleted.

0.4.9

  • This Mac in the app is now the same page as in the browser. Its version, restart, what the Mac is used for, keeping it awake, what it can build and disk space, in one place for every device.
  • Install from Settings. A missing tool has its Install or Set Up button right in the list; it opens Terminal and shows the command before anything runs. Check Again looks at the Mac anew.
  • Your notifications stay on this Mac. Failed and passed runs, and the load in the menu bar, are set in the same page, in the app.
  • Start from Settings. If Great_git is not running, the window says so and has a Start button.
  • Settings look like one window. Projects, Phone & Web and This Mac have the same size of text and buttons as the other panes, and the pane you are in stays highlighted in the sidebar while you work in it.

After updating: nothing to do. AI Assistants, More Macs and Advanced in

the app are still the app's own panes.

0.4.8

  • Runs start by themselves. Turn on watching for a project and a push to a branch, or a change in a pull request, starts its checks on this Mac, with the result shown on GitHub. Nothing has to be opened to the internet for it.
  • A release is not a test. A check that signs an app, uploads a build or deploys can no longer be started by a device that may only run and cancel, even when a push normally starts it. It takes the right to release, and the list of checks says why.
  • A browser you use stays signed in. Each visit moves the end of its sign-in 90 days ahead, up to a year from the day it signed in. A phone left in a drawer is signed out as before.
  • Another Wi-Fi no longer brings the certificate warning back. The Mac keeps the same certificate when its network changes, so a phone that accepted it once and an AI assistant that trusts it keep working.
  • Claude Code and Codex on this Mac connect with no key to copy.
  • If you run your own relay: a burst of requests can no longer stop people from adding their Macs, and gg-relay user token <name> gives a person a new key and ends the old one everywhere.

After updating: nothing to do. A phone that reaches this Mac by a bare

address instead of its name may ask about the certificate once more, on

a network it has not been on before.

0.4.7

  • Settings in the app and in the browser are now the same pages. Projects and Phone & Web in the app's Settings window show exactly what your phone shows under Settings, so the two can no longer drift apart.
  • Choose Folder is still one click. In the app, a project is added with the system's folder chooser; a Git address works there too.
  • Each device with its own rights, in the app as well. Change… and Remove for every phone and laptop, and the list follows by itself when a phone scans the code.
  • Test builds moved to Settings, then Advanced.

After updating: nothing to do. This Mac, AI Assistants, More Macs and

Advanced in the app are still the app's own panes; they move to the

shared pages in the next builds.

0.4.6

  • Advanced in the browser. Settings in the dashboard has a fourth page, Advanced: one line for each topic, opened one at a time.
  • Activity: who did what. A record of what was done from other devices (a run started or cancelled, a project added, a device changed, a secret written), with the device's name and what this Mac refused.
  • Secrets for runs, written and never shown back. Add, replace or remove a key your checks need from the browser. No page and no request can read a value afterwards.
  • Access keys in one list. Every key an AI assistant or a script signs in with: what it may do, for which projects, when it was last used, and Remove.
  • What this Mac is reachable by: its address and certificate, a server of your own if one is linked, other Macs that share the work. Shown here; changed on the Mac, so the page cannot lock you out.
  • About: version and details to copy for support.

After updating: a secret written from the browser is used by runs after

Great_git restarts; the page says so and leads to Restart.

0.4.5

  • Keep this Mac awake works with the app closed. Great_git itself now holds the Mac awake, in the background, so runs can start at any time even after you quit the app from the menu bar. Before, it held only while the app was open.
  • Turn it on from your phone. The same switch is in the browser, under Settings, then This Mac, for a device that may manage this Mac.
  • The choice survives a restart of Great_git and of the Mac.

After updating: if Keep this Mac awake was on, it stays on; the app hands

your choice over the first time it opens. Nothing to do.

0.4.4

  • Settings in the browser. The dashboard has a fourth section, Settings, with the same questions as the app: Projects, Phone & Web, This Mac. A Mac without a monitor can now be set up from a phone or a laptop.
  • A third choice in See on My Phone: Manage this Mac. A device you give it to sees Settings. It is given only on the Mac, to one device at a time, and a link made from the browser never carries it.
  • Each device has its own rights. In Phone & Web every phone and laptop is listed with what it may do (look, run and cancel, or manage) and its own Change… and Remove. Before, one switch applied to all.
  • Projects from the browser: add one by its Git address, run it, remove it. A folder that is already on the Mac is still chosen on the Mac.
  • This Mac from the browser: what it can build, disk space with Free Up Space, what the Mac is used for, and Restart, which says how many steps it would stop and waits for the Mac to come back.
  • The dashboard on the Mac itself opens with Settings: the browser of this Mac manages it without any code.

After updating: devices that were already signed in keep what they had.

To manage this Mac from your phone, open See on My Phone, choose Manage

this Mac and scan the new code. AI assistants, more Macs, addresses and

secrets are still set in the app, under Advanced: they move to the

browser in the next builds.

0.4.3

  • Your ci runs on any branch. A check that GitHub starts for pull requests can now be started on a feature branch: Great_git runs it as for a pull request into your main branch. Before, it was greyed out with "Runs on its own schedule or on tags".
  • Nothing in the list is a dead row any more. A check that starts by itself only on another branch or on a schedule can still be run at this Mac, and the list says why it is not offered first.
  • A project without workflow files is not a dead end. If the project keeps no checks of its own, Great_git offers the ones a project of its kind has: Flutter and Dart, JavaScript (npm, pnpm, yarn, bun), Swift packages, Gradle, Rust, Go, Python, and make test, also for a project one folder down. Each says what it runs.
  • A clearer answer when there is nothing to run: which commit was looked at, what was looked for, a branch picker, and a reminder that a check you have just added is seen once it is committed.
  • Run Again works for every run, including one you started past its triggers.

After updating: nothing to do. Open the project again and choose what to

run.

0.4.2

  • Updating finishes by itself. After you install a new version, the part of Great_git that works in the background is restarted, so it is the same version as the app. Before, it stayed the old one until the next login, and adding a project failed with a technical message.
  • It asks when a run is going. If steps are running at that moment, nothing is stopped: the menu shows "Restart to finish updating" and waits for you.
  • A plain message instead of a technical one if the app and the background part ever disagree, with what to do.

0.4.1

  • Run your tests from the app. Add a project by choosing its folder, pick what to run, and watch it step by step. No terminal.
  • A Welcome window on first launch that says what to do next, with "Run a Test Check" to see a green run before you add anything.
  • A simpler menu: what is happening now, one button to run, the last runs, and a card only when something needs you.
  • See on My Phone: a QR code that signs one phone in. It works once and for ten minutes. Each device is listed and can be removed, and you choose whether it may only look or also run and cancel.
  • Run from the phone too. The dashboard has a Run… button, and it opens on this Mac without a key or a certificate warning.
  • Settings by question: Projects, Phone & Web, This Mac (with what this Mac can build). The technical panes moved under Advanced.
  • A notification when a run fails, and an option to keep the Mac awake so runs can start any time.

After updating: sign-in links and QR codes made by an earlier build keep

working until they expire. If one was shared, remove it in Settings under

AI Assistants (it is listed there as "dashboard").

0.4.0

  • Nothing to set up. On first launch the app installs itself, starts and checks which tools this Mac has.
  • A dashboard in the browser with runs, logs, test videos and screenshots, made for a phone first.
  • Connect Claude Code or Codex in two steps, so an AI assistant can run your checks on this Mac.
  • Reach the Mac from outside your network through a relay, without opening a port.
  • Screen recordings of Maestro tests, kept for the runs that failed.
  • Questions before work is lost: cancelling a run, restarting or stopping Great_git, removing a project or an access.
  • An app icon, and a menu that says when something needs you.