cookiesync
Sync your browser cookies across machines — land on a new laptop already logged in.
cookiesync copies the cookies your browser already holds on one machine and replays them on another, reusing your live session instead of asking for passwords again — so logins, 2FA, and SSO state carry over without re-authenticating. It's browser-agnostic, and you pick which machines and which sites it touches. Automation can borrow a logged-in session too: hand a CI job or an agent the cookies it needs, never a password.
macOS only. cookiesync keeps your browser's Safe Storage key behind a Touch ID prompt and a Secure Enclave–bound daemon, so decrypted cookies never land on disk. The key helper is a Developer-ID-signed, notarized
.app.
Install
Install the cookiesync command with uv:
uv tool install cookiesync-cli
cookiesync --help
Quickstart
# Fetch the signed key helper and install the LaunchAgents (one time)
$ cookiesync install
Installing the signed key helper via Homebrew (brew install yasyf/tap/cookiesync-keyhelper)…
Installed and verified key helper: /Applications/cookiesync-keyhelper.app
Installed cookiesync agents.
# Track a browser to sync between this Mac and another host
$ cookiesync browser add other-host chrome
Tracking other-host/chrome/Default
# Hand a logged-in session to a script — no password
$ cookiesync cookies https://example.com --browser chrome
Once a browser is tracked, the resident daemon watches its cookie store and converges
it across your hosts. Run cookiesync reconcile to force a full pass.
Commands
| Command | What it does |
|---|---|
install |
Fetch the signed key helper, then install the LaunchAgents (watch daemon + reconcile tick). |
uninstall |
Remove the cookiesync LaunchAgents. |
doctor |
Check that the key helper is installed and Developer-ID signed. |
browser add/ls/rm |
Track, list, and untrack the browser profiles cookiesync syncs across hosts. |
watch |
Run the resident sync daemon: watch local stores and serve the RPC socket. |
sync --browser <name> |
Converge one browser group across this host and its peers. |
reconcile |
Run a full reconcile pass over every tracked browser group. |
auth |
Release the Safe Storage key behind one Touch ID tap and cache it for a short window. |
cookies <url> |
Stream a URL's cookies in the chosen format (Playwright by default). |
self |
Print this host's SSH target, as reposync reports it. |
rpc <method> |
Low-level RPC client for the resident daemon. |
Run cookiesync --help, or cookiesync <command> --help, for the full reference.
How it works
cookiesync install fetches the notarized key helper and starts a resident daemon. The
daemon watches each tracked browser's cookie store, and on a change it converges that
group across your hosts over SSH — extracting and re-applying cookies through the same
RPC the peers speak. Decryption needs the browser's Safe Storage key, which the helper
releases only behind a Touch ID tap (cookiesync auth) and caches in the
Secure-Enclave-bound daemon for a short window, never on disk.
License
PolyForm Noncommercial 1.0.0 — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for cookiesync-cli 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| cookiesync_cli-0.2.0.tar.gz | 48.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| cookiesync_cli-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 111.8 kB
Release files / cookiesync_cli-0.2.0.tar.gz
| Download URL | cookiesync_cli-0.2.0.tar.gz |
|---|---|
| Size | 48.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
145b499860f3e76f34e05761d947c70f16e944f23e4958a2b672dd157b641d88
|
|
BLAKE2b-256 checksum How to use checksums |
85aa3a6e60da8467e0d4f210216025c25a14e5482c5b4e76d34662516bc0c63b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logRelease files / cookiesync_cli-0.2.0-py3-none-any.whl
| Download URL | cookiesync_cli-0.2.0-py3-none-any.whl |
|---|---|
| Size | 63.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ef44b313e6901e5907d3241ce56621c00f134cfcee9868c0557bd429b6a4f4d3
|
|
BLAKE2b-256 checksum How to use checksums |
94e27d470900144074ac6a9715909afa92ab2c3e7d0675dbaeb9ce09a8a90616
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logSecurity for cookiesync-cli 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for cookiesync_cli-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
