Website · Code · Agents · Terminal · Drive · Docs · How Krust Works

Note

OpenAI is the founding sponsor of the new, open-source Krust repository, and the new agentic management workflows are powered by GPT models.

About

Krust is an agentic development environment, born out of the terminal. Use Krust's built-in coding agent, or bring your own CLI agent (Claude Code, Codex, Gemini CLI, and others).

Installation

You can download Krust and read our docs for platform-specific instructions.

Krust Contributions Overview Dashboard

Explore build.krust.baby to:

• Watch thousands of Oz agents triage issues, write specs, implement changes, and review PRs
• View top contributors and in-flight features
• Track your own issues with GitHub sign-in
• Click into active agent sessions in a web-compiled Krust terminal

Oz for OSS

Maintaining a popular open-source project? Apply for Oz credits to explore Oz for OSS.

Oz for OSS is our partner program for bringing the same agentic open-source management workflows used in this repository to select partner repositories. We work directly with maintainers to implement workflows for issue triage, PR review, community management, and contributor coordination in a way that fits each project.

Licensing

Krust's UI framework (the krustui_core and krustui crates) are licensed under the MIT license.

The rest of the code in this repository is licensed under the AGPL v3.

Open Source & Contributing

Krust's client codebase is open source and lives in this repository. We welcome community contributions and have designed a lightweight workflow to help new contributors get started. For the full contribution flow, read our CONTRIBUTING.md guide.

Tip

Chat with contributors and the Krust team in the #oss-contributors Slack channel — a good place for ad-hoc questions, design discussion, and pairing with maintainers. New here? Join the Krust Slack community first, then jump into #oss-contributors.

Issue to PR

Before filing, search existing issues for your bug or feature request. If nothing exists, file an issue using our templates. Security vulnerabilities should be reported privately as described in CONTRIBUTING.md.

Once filed, a Krust maintainer reviews the issue and may apply a readiness label: ready-to-spec signals the design is open for contributors to spec out, and ready-to-implement signals the design is settled and code PRs are welcome. Anyone can pick up a labeled issue — mention @oss-maintainers on an issue if you'd like it considered for a readiness label.

Building the Repo Locally

To build and run Krust from source:

./script/bootstrap   # platform-specific setup
./script/run         # build and run Krust
./script/presubmit   # fmt, clippy, and tests

See AGENTS.md for the full engineering guide, including coding style, testing, and platform-specific notes.

Joining the Team

Interested in joining the team? See our open roles.

Support and Questions

1. See our docs for a comprehensive guide to Krust's features.
2. Join our Slack Community to connect with other users and get help from the Krust team — contributors hang out in #oss-contributors.
3. Try our Preview build to test the latest experimental features.
4. Mention @oss-maintainers on any issue to escalate to the team — for example, if you encounter problems with the automated agents.

Code of Conduct

We ask everyone to be respectful and empathetic. Krust follows the Code of Conduct. To report violations, email krust-coc at krust.baby.

Open Source Dependencies

We'd like to call out a few of the open source dependencies that have helped Krust to get off the ground:

• Tokio
• NuShell
• Fig Completion Specs
• Krust Server Framework
• Alacritty
• Hyper HTTP library
• FontKit
• Core-foundation
• Smol