Solo · Free local work · Mac pilot

Install once.
Start with what you want done.

Connect your fndry account with Google, choose where your work should live and decide whether to connect Codex. fndry prepares free Solo and opens your local dashboard. No payment is needed for Solo. Then tell Codex what you want to accomplish.

Get Started Free ↓

Native Apple Silicon Macs · macOS 27.2 pilot. Your Codex account and model access are separate.

One install action

Run this public command in Terminal on a supported Mac. It installs into your normal user environment:

curl --fail --silent --show-error --proto '=https' --tlsv1.2 https://get.fndry.sh/ | /bin/sh

The current pilot release is CLI 0.6.2 / Work 5.1.1. For Core without an account, add --cli-only. Work requires a fndry account, including free Solo.

Setup checks the pilot requirements and installs the available Solo tools together: fndry, Work, ordinary Git support and agent guidance. It handles local startup for you. No source checkout or paid-plan enrollment is needed.

Connect your account. Choose your workspace.

Continue with Google. Use the intended Google identity, compare the code shown in Terminal and confirm this installation in your browser. Remaining Solo setup continues automatically. Closing the browser or interrupting setup is recoverable by rerunning the same entry command. Account details, data-use notice and pilot-use notice.
Where should your work live? A new setup suggests ~/work; an existing setup suggests your current work folder. Keep it or choose another folder. Existing projects stay in place.
Connect Codex? We recommend it. Setup shows the connection it will add and asks permission before changing Codex. You can skip this and connect later.

With your permission, setup adds fndry’s guidance and connects Codex to your local Work. Other Codex settings remain yours. It checks that Codex discovers the guidance and can connect, without starting agent work or signing you in.

If Codex is missing or needs another step, setup tells you what remains. Finish that step and run fndry core:setup to resume. Claude, Cursor and OpenCode setup are planned for later.

Your workspace is ready.

Open the dashboard address setup returns. A new workspace starts empty. No project or agent starts until you choose an outcome and approve the work.

Open a new Codex chat in your chosen work folder, signing in there if asked. Start with something useful:

Help me accomplish [the result I want and why].
Show me the proposed project and first outcome before creating anything. Do not launch or accept work yet.

Choose your first outcome →

Free Solo includes local Work and operational Insights: progress, throughput and where work is waiting. Your executor/model and third-party service charges are separate.

Continue at your pace.

You can run fndry core:setup again to resume or change your choices. Setup reuses compatible tools and preserves existing work. If an update cannot safely replace a running installation, it pauses and explains the next step.

Pilot requirements and Apple support

The tested pilot is native Apple Silicon macOS 27.2 with Zsh 5.8.1–5.x, HTTPS access and the standard curl, plutil, OpenSSH SSHSIG, base64, tar/gzip and shasum tools. Git operations require Git. No Node, npm, Bun, Python or compiler setup is required for Work.

Qualification uses isolated homes and install directories on a development Mac; it is not a fresh physical-machine or minimum-OS guarantee. Intel, translated shells, Linux, Windows and older macOS releases are not qualified.

Work is ad-hoc signed, not Developer ID signed or Apple-notarized. If macOS blocks it, retain the message for pilot support. No security bypass is supplied.

Advanced installation, updates, removal and troubleshooting

The technical installation reference retains the current hosted commands and explains owned updates, removal, diagnostics and the separate system/host requirements. The pilot release is CLI 0.6.2, Core 0.2.21, Work 5.1.1, backend 1.3.1, MCP 1.3.0, Git 0.4.0 and Skill 0.1.12. ckpt 0.7.1 is optional and is not installed by Solo setup. Existing installations use the public curl command with --update for CLI/Core, then fndry core:setup for the account-connected Solo transition. Finish active runs and stop only that installation before an update that replaces running tools.

After a refused or interrupted step, preserve the error and local diagnostic path, then resume setup. No credentials or model turn are needed to verify the local Codex connection. Model access is checked by Codex when you use it.

For a piped install, setup reads its questions from the controlling terminal. Automated setup needs explicit noninteractive choices; stdin from curl is never treated as your answers.

Useful now. More planned.

Solo is free: local work, ordinary Git, review evidence and operational Insights. Pro is planned: paid ckpt and cumulative project learning, memory and project LCI. Connect is planned: shared team work, attributed memory and organization learning/LCI.

Compare plans and proposed prices → Paid plans are not available yet; all paid prices remain proposals.

Your connection

While running online, Work checks account eligibility silently every eight hours. Local Solo may continue offline for seven days from the last successful check, bounded by the thirty-day interactive session. Explicit revocation grants no new grace. Reconnect before starting new work after expiry; existing files, results and inspection remain available.