CrewKite 0.1.0

CrewKite 0.1.0

CrewKite runs the coding agents you already pay for, Google, OpenAI, Anthropic and a local model, as one crew on your own computer.

What it does

• Crews: give each role its own provider, model and effort. The default crew plans with Anthropic, builds with OpenAI, fixes with Google, reviews with OpenAI, challenges with Anthropic and answers side questions on a local model. Roles can start subagents.
• Limit handoff: when a provider runs out of included allowance, the thread moves to the next connected provider with its messages and edited files.
• Allowances in view: the rail shows each provider's usage windows and their reset times. The kite meter shows what the next message will use before you send it.
• Credits stay off: Allow credit spending is off by default for OpenAI and Anthropic. A step that would spend credits moves to another provider before it starts.
• Your checkout stays as it is: each thread works in its own copy of the repository. Review the changes, then accept them.
• Flight mode and Permissions decide how much the crew does on its own and which commands it may run without asking.
• Run tests runs your project's test command in the thread's copy and shows the exit status and output. No model turn, no credits.
• Connect each provider once in Settings. CrewKite reconnects on its own after a restart, Local included.
• Check for Updates in the app menu, plus one quiet check a day.
• A CLI for the same crews and threads.

Platforms

• macOS on Apple silicon, signed with Developer ID and notarized.
• Linux x64 and arm64 as DEB and RPM, a preview. The DEB was tested on Ubuntu 24.04 with desktop launch. The RPM was tested on Fedora 45 for install and headless runtime and CLI. Google is not available on Linux.
• Windows is not supported yet.

Requirements

Each provider's own client, signed in on your computer: OpenAI from 0.163.0, Anthropic from 2.1.259, the Google quota reader from 1.4.0. A local model needs LM Studio.

Verify

Check each download against SHA256SUMS with shasum -a 256 on macOS or sha256sum on Linux.

D2b UAT 05: project model selection

This preview makes OpenAI Project model and effort choices available before a planning conversation.

Open Project preparation to read the supported native client catalog. Choose an advertised model and effort, review the task, then Start. CrewKite retains the exact choice and checks it again before execution. Catalog discovery starts no model turn. Stop and restart preserve metadata ownership and uncertain outcomes.

The provider setup, hardware, task-entry and Anthropic usage improvements from UAT 04 remain included. New Project execution remains OpenAI-only. Broader repository work and the other provider Project engines are under development.

Validation passed 146 Node tests, the desktop journey and required CI. Offline fixtures cover model-choice binding and metadata lifecycle. Live account discovery and alternate-model execution have not been qualified for this release. Human UAT remains pending.

Download the ZIP, release.json and SHA256SUMS together. This is an ad-hoc signed macOS Apple silicon preview with the documented folder-scoped trust step. It is not notarized.

CrewKite by Roots No Limits LLC. Created by Raymond J. Kraft.

D2b UAT 04: subscription usage reports

This preview adds manual Anthropic subscription usage refresh and reported allowance gauges.

Choose Refresh Anthropic quota in Connect providers. The first read asks for trust in the installed native client and its local usage command. CrewKite sends no generation request for that read. Reported percentages appear as remaining allowance; the native report does not supply its observation time, so cache age stays unknown. Reports survive restart, and Stop remains available during a read.

The task and provider setup improvements from UAT 03 remain included. New Project execution is available through OpenAI. Broader repository work and other provider Project engines remain under development.

Verification covers offline protocol, ownership, retention, renderer and desktop behavior. Live Anthropic subscription usage has not been qualified for this release. Human UAT remains pending.

Download the ZIP, release.json and SHA256SUMS together. The package remains an ad-hoc signed macOS Apple silicon preview with the documented folder-scoped trust step. It is not notarized.

CrewKite by Roots No Limits LLC. Created by Raymond J. Kraft.

D2b UAT 03: project tasks and provider setup

This preview replaces the task setup that led into a single-file proposal. New task opens the task definition directly, and the project-row action keeps the project selected. OpenAI Project prepares a separate working copy with one explicit project permission and subscription-only defaults.

• Combine Local connection and model discovery, save the model selection immediately, and poll readiness with a refresh fallback.
• Advance Google connection through the applicable installation, initialization, sign-in and discovery steps.
• Keep quota feedback on its provider card. Report all four activity families, cloud credit status and local CPU/memory facts.
• Add selected Python unittest candidate checks and retained GitHub Actions status/log reads.
• Show the Roots local-AI code card. Attribute CrewKite to Roots No Limits LLC and its creator, Raymond J. Kraft.

Verification passed 139 Node claims and one desktop journey, required CI, package inventory/dependencies/notices/signatures, archive-derived task entry and same-home reopen, and a disposable upgrade from schema 15 to 16. Read-only GitHub workflow and job-log checks also passed with retained raw-byte and rendered-text evidence. Human UAT remains pending.

Normal new-task execution offers OpenAI Project in this release. Local, Google and Anthropic Project integration remains in progress; saved file runs and CLI single-file support remain compatible. Model and effort choices use a catalog retained by a successful planning turn; the profile default applies before that observation. Anthropic standalone quota refresh is not included in this candidate.

This is a macOS arm64 engineering preview with an ad-hoc integrity seal, without Developer ID signing or notarization. Verify SHA256SUMS and follow the folder-scoped trust and upgrade instructions in docs/preview.md and docs/distribution.md. Keep the existing installation and home in place while using Upgrade Existing. Read release.json for exact evidence and limits.

D2b UAT 02: large output and activity history

D2b UAT 02

This slice adds complete activity-history navigation and reads large retained output through small pages. Full-output verification runs incrementally and can be cancelled. Output reads leave Stop and workspace status available. The provider setup and project-recovery corrections from D2b UAT 01 are included.

Download the ZIP, release.json and SHA256SUMS together. From that download folder, run:

shasum -a 256 -c SHA256SUMS

Extract after verification passes. The ZIP includes the README, complete documentation and the upgrade helper. Human UAT remains pending.

First launch

The runtime has a verified ad-hoc resource seal. It has no Developer ID identity and is not notarized by Apple. For the checksum-verified folder named exactly d2b-uat-02 in Downloads, preserve its download metadata and trust only that folder:

(
  set -e
  set -C
  /usr/bin/xattr -l -r -s -x "$HOME/Downloads/d2b-uat-02" > "$HOME/Downloads/d2b-uat-02.quarantine-before.txt"
  /usr/bin/xattr -d -r -s com.apple.quarantine "$HOME/Downloads/d2b-uat-02"
)

This changes no global Mac security setting. A failed checksum or strict signature check needs a corrected package. Open CrewKite.command for a new workspace. Opening Electron.app directly shows the runtime screen.

Keep an existing workspace

Quit the existing preview and keep the fresh replacement unopened. Run Upgrade Existing.command from the verified replacement, choose the existing package folder and inspect the installed and backup paths before confirming. After success, reopen CrewKite.command at the original installed path. Keep the backup and original ZIP. Do not launch the backup at its new path or move initialized state between packages.

The upgrade guide covers refusal and restoration. Memory-only Local tokens need re-entry after restart; explicit Local connection configuration is retained.

What to try

Start with provider setup and project recovery. Connect providers is available before adding a project. OpenAI reports subscription usage or an actionable read failure. Anthropic offers a native sign-in check; its standalone allowance remains unknown. Google guides installation, initialization, personal sign-in and discovery. Local uses its configured loopback runtime. The provider guide separates client availability, authentication, allowance and coding qualification.

For this slice, open an existing task's Activity view. Traverse older and newer history and return to the latest entries. An oversized retained activity entry offers Read output, Next output page and Verify complete output. A displayed page remains explicitly unverified until the complete checksum succeeds. Cancel verification and check that navigation and Stop remain available. Small tasks may have no oversized entry.

The packaged CLI also supports artifact read, verify and verified save commands, and complete activity pages. See the CLI guide. Reopen the same installed workspace and check that its tasks, projects and Local settings remain.

General project commands, large source capture, multi-file evaluation and GitHub workflows remain separate daily-work slices. This release does not establish coding parity or D3 acceptance.

Verification

Source 466f9f7 matches the merged main tree. Matching local verification and required CI passed 111 Node claims and one desktop journey. Inventory, installed dependencies, 29 notices and strict ad-hoc signatures passed.

An exact GitHub-client download matched the ZIP checksum. Its native archive extraction passed normal cold launch and same-home reopen on macOS 27.0.1. Chrome blocked the asset navigation in this environment before creating a file; an actual Chrome download and inherited-quarantine launch were not qualified for this exact ZIP. The prior release retains its separate successful browser-download proof. No global security setting was changed.

A disposable copy of D2b UAT 01 passed an in-place upgrade with exact target and backup state preservation, migration 14 to 15, pending project-command recovery, valid project registration and retained Local configuration through reopen. The existing user installation was not modified. Qualification submitted no provider prompts or paid API calls. Actual disk-full behavior and human UAT remain pending.

D2b UAT 01: provider setup and project recovery

D2b UAT 01

This candidate replaces D2 UAT 02 for the next usability pass. It repairs provider setup, OpenAI usage feedback and the project-selection retry loop. Workspace and task lists use complete pages. It includes a helper for upgrading an existing preview at its original path while retaining a backup.

Download the ZIP, release.json and SHA256SUMS together. From that download folder, run:

shasum -a 256 -c SHA256SUMS

Extract only after verification passes. The ZIP contains the public README and the complete documentation. Its release receipt records the exact source, verification and observed launch and upgrade scope. Real-project UAT remains pending.

First launch

The runtime has a verified ad-hoc resource seal. It has no Developer ID identity and is not notarized by Apple. For the checksum-verified folder named exactly d2b-uat-01 in Downloads, preserve its download metadata and trust only that folder:

(
  set -e
  set -C
  /usr/bin/xattr -l -r -s -x "$HOME/Downloads/d2b-uat-01" > "$HOME/Downloads/d2b-uat-01.quarantine-before.txt"
  /usr/bin/xattr -d -r -s com.apple.quarantine "$HOME/Downloads/d2b-uat-01"
)

This changes no global Mac security setting. A failed checksum or strict signature check needs a corrected package.

For a new workspace, open CrewKite.command. Opening Electron.app directly shows its runtime screen.

Keep an existing workspace

Quit the existing preview and keep the fresh replacement unopened. Run Upgrade Existing.command from the verified replacement, choose the existing package folder and inspect the installed and backup paths before confirming. After success, reopen CrewKite.command at the original installed path. Keep the backup and the original ZIP. Do not launch the backup at its new path or move an initialized state folder between packages.

The upgrade guide explains refusal and restoration behavior. Memory-only Local tokens need re-entry after restart; the explicit Local connection configuration is retained.

Connect providers first

Choose Connect providers before adding a project. OpenAI reads the supported native client's subscription session and reports usage-read failures. Anthropic has a native sign-in check; its standalone allowance remains unknown. Google installs the reviewed official ACP client, then guides Initialize, Sign in and Discover. Google quota readings alone do not establish that connection. Local uses its separately configured loopback connection and loaded model.

Use the provider guide for supported client versions and native sign-in instructions. A metadata check submits no coding prompt and does not establish a qualified execution route.

Try the usable path

Follow the preview guide: connect a provider, add a small Git repository, create a task, discuss and adopt a plan, then prepare and run a small supported change. Check Changes, use the offered checks and review, accept to a new local branch, quit and reopen the same home. A refused project folder should allow another selection after its exact saved command settles.

Large source capture, general project commands, GitHub workflows and larger content retrieval remain separate daily-work slices. The ten retained D2 task outcomes remain historical task evidence, separate from this candidate's installed usability and current UAT.

Source db0b8a1 matches the accepted main tree. Matching verification passed 109 Node claims and one desktop journey, with required CI green. Inventory, dependencies, 29 notices and the ad-hoc signatures passed. The actual Chrome-downloaded ZIP passed checksum verification, normal cold launch and same-home reopen after the documented folder-only trust step on macOS 27.0.1.

A disposable copy of D2 UAT 02 passed the installed upgrade with exact target and backup state preservation, migration 13 to 14, pending project-command recovery, valid project registration and retained Local configuration through reopen. The existing user installation was not modified. Human UAT remains pending.

D2 UAT 02: failed UAT, replaced

UAT status: failed, replaced

This candidate is retained for issue reproduction. Use D2b UAT 01 for the next usability pass. Its release instructions include the verified download trust step and an original-path upgrade that retains state and a backup. Human UAT remains pending.

Observed blockers include macOS download launch, a failed project selection that can leave a command pending across restarts, and incomplete provider setup and usage feedback. Google quota readings do not establish an ACP coding connection. Anthropic client readiness is hidden when no route exists, and the OpenAI quota reader can fail without an actionable status.

The ten retained checked-task outcomes below remain separate from installed usability. They do not establish a passed UAT. Corrections are being reviewed and published in stages under D2b, followed by a new package and same-home recovery evidence.

The runtime seal repair, workspace paging and project-selection recovery, provider setup, and installed-upgrade correction have merged after required CI passed. The published D2b UAT 01 replacement passed matching 109 Node claims and one desktop journey, download checksum verification, installed cold launch and reopen, and a disposable original-path upgrade with complete target and backup state preservation. These repairs do not change the retained assets below.

---

Known first-launch issue in this candidate

The checksum-verified ZIP can still be rejected by macOS because its copied runtime lacks a complete resource seal and downloaded executables retain quarantine. A corrected candidate is in preparation. The commands below describe the observed local recovery for this exact candidate; they do not provide Developer ID identity or Apple notarization.

After verifying both entries in SHA256SUMS, these commands assume the extracted folder is exactly $HOME/Downloads/d2-uat-02:

codesign --force --deep --sign - "$HOME/Downloads/d2-uat-02/Electron.app"
codesign --verify --deep --strict --verbose=2 "$HOME/Downloads/d2-uat-02/Electron.app"
xattr -prx com.apple.quarantine "$HOME/Downloads/d2-uat-02" > "$HOME/Downloads/d2-uat-02-quarantine-backup.txt"
xattr -dr com.apple.quarantine "$HOME/Downloads/d2-uat-02"
"$HOME/Downloads/d2-uat-02/CrewKite.command"

The quarantine step explicitly trusts only that verified extracted folder. Global Mac security settings remain unchanged. Keep the backup locally. The runtime seal changes local executable signatures, so the original file inventory describes the downloaded bytes before this repair. The ZIP checksum stays unchanged.

Opening Electron.app directly can show its default runtime screen. Quit that window and use CrewKite.command to open the actual workspace. The affected local copy was observed opening CrewKite with its controller connected after the repair. This establishes that recovery on the observed device, with the stated manual steps.

D2 UAT preview for macOS arm64. Ten distinct backlog outcomes completed checks, separate native review, branch acceptance and same-home reopen. The exact assisted repair scope and historical evidence limits are recorded in release.json.

Download all three assets below: crewkite-macos-arm64-d2-uat-02.zip, SHA256SUMS and release.json. From the download folder, verify them:

shasum -a 256 -c SHA256SUMS

Extract the ZIP, keep its folder together and double-click CrewKite.command. Reopen that same folder to retain projects, tasks and settings. This is a directory preview rather than an installer. Follow the UAT instructions.

Provider setup

OpenAI uses the installed Codex CLI and Anthropic uses Claude Code, with each user's own login. D2 pins supported builds (Codex 0.163.0 and Claude Code 2.1.302); an unsupported build is reported rather than silently substituted. Keep paid extra usage disabled and review the task permissions. There is no shared CrewKite login for all providers.

Google uses the separate pinned ACP agent. It currently needs a manual client import, then Initialize, Authenticate and Discover; an existing Antigravity login alone does not configure a fresh CrewKite home. Use the advertised Flash selection, with no paid-credit fallback. See the provider setup and exact route boundaries.

For Local, start LM Studio and load one eligible model with an 8,192-token context. Configure the loopback connection, connect, refresh models and select the observed model. Dedicated-token input is requested again after restart. Discovery does not load or download models. The CLI guide describes both explicit authentication modes; use ./bin/crewkite in this package in place of the source guide's pnpm crewkite prefix.

First UAT pass

Use a small disposable Git repository with an initial commit, a configured Git identity and a committed Node test supported by the offered check recipe. Select that exact test file for checks; arbitrary package-manager commands are not supported yet. Use the supported OpenAI planning profile for the initial discussion. Create a task, discuss and adopt a plan, prepare one small committed text file, inspect permissions and Start. Select another provider only for an execution role it advertises. Inspect Changes, run the offered matching checks and independent review, then approve acceptance to a new local branch. The original checkout stays unchanged. Quit and reopen the same package folder and confirm retained task and evidence. Try providers separately before combined work. Allow 30–60 minutes for a useful first pass, excluding provider setup.

Report the candidate, provider/model, expected and actual behavior, exact refusal and a screenshot where useful. Exclude credentials. Large repositories, general commands and tests, Git push, GitHub PR and Actions workflows, and large-history handling belong to the next daily-work slices.

Verification and limits

The package is bound to source 32bc92e, matching 95 Node checks and one desktop journey, inventory and notices, and empty-workspace cold launch plus same-home reopen from this exact ZIP on macOS 27.0.1 build 26A434. Main-branch CI passed.

This preview is unsigned and unnotarized. Fresh-machine installation, Gatekeeper behavior and the declared minimum OS remain unqualified. Retain any opening refusal with the candidate identity. Exact route observations do not qualify every model or operation; active Google Stop and installed recovery keep their separate gates.

Real-project UAT and any required D2c corrections precede separately approved D3 distribution work.