curie-eng/curie

**Turn agents into co-workers. Run them in your infrastructure. Start with a Software Factory co-worker**
Curie brings agents into the workspaces your team already uses. Delegate work,
follow progress, approve restricted actions, and inspect the result. The platform
is Apache-2.0 and runs in your infrastructure, with shared memory facilities,
model configuration, and cost visibility.
Start with a **Software Factory co-worker**. Use Codex, Claude Code, or another
coding agent to help investigate and specify a bounded GitHub, GitLab, or Jira
Cloud issue. Delegate the issue to Curie for implementation and review; it
returns a pull request or merge request for your team to accept. You can also
deploy an **SRE co-worker** for Kubernetes investigations, or adapt an existing
agent's instructions and tools to the same platform.
| Start here | First outcome |
| --- | --- |
| Software Factory | Label an issue and get a reviewed PR or merge request, or a clear failure reason. |
| SRE co-worker | Ask about your local cluster in Slack; approve configured mutations. |
| Bring your existing agent | Reuse its instructions and tools, then connect it to a workspace. |
See the Software Factory
Watch the Software Factory demo, then
follow the local quickstart below. The video features GitHub; the quickstarts
also cover supported GitLab and Jira Cloud paths.
Quickstart
The software factory and SRE co-workers below run on **local kind clusters**. They use the
same platform you can later install on your own Kubernetes infrastructure.
You need Docker running, kind, kubectl, Helm, and an Anthropic or OpenRouter
model credential. Use a Bash terminal and keep the variables in that session.
Allow enough Docker memory and disk for Curie and the SRE observability stack.
The factory prerequisites
list supported machines and tools.
Install the released CLI:
Enter your model credential without echoing it, then select a model available
through that provider. For OpenRouter, use its full provider/model identifier.
Software Factory on your laptop
Choose where your issues and code live:
| Issues | Code and result | Start here |
| --- | --- | --- |
| GitHub | GitHub pull request | Follow the GitHub steps below |
| GitLab | GitLab merge request | GitLab quickstart, for gitlab.com or self-managed GitLab |
| Jira Cloud | GitHub pull request | Jira Cloud with GitHub quickstart |
| Jira Cloud | Bitbucket Cloud or Data Center pull request | Jira Cloud with Bitbucket quickstart, for Bitbucket Cloud or Data Center 9.4.0 or later |
GitHub
Create a GitHub repository with an initial commit, or use a small existing
repository. Write a bounded issue with clear acceptance criteria.
**1. Start the local factory setup.** A dedicated kubeconfig keeps this trial
separate from your other clusters.
The command creates a local kind cluster, installs Curie, and prints a GitHub
App registration link. Open that link, create the App, generate its private key,
and install it on the selected repository. Note the App ID and the absolute
path of the downloaded key file.
On Apple Silicon, an older released chart can stop here with an AVX preflight
error. ARM64 does not use x86 AVX. Recover only that architecture-specific
failure in this trial cluster, then rerun the quickstart command using the
same variables. Do not repeat the cluster-name or kubeconfig initialization:
The current source chart detects native ARM64 with the preflight enabled.
Keep the check enabled on x86. See the
ARM recovery details.
**2. Complete the setup with your App.**
**3. Delegate the issue.** Add the curie-factory label in GitHub. The person
adding it needs write or admin access to the repository.
The issue status comment shows progress through planning, implementation, review,