- Rust 98%
- Shell 0.8%
- Python 0.4%
- Objective-C 0.3%
- PowerShell 0.1%
- Other 0.1%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
02fbb3bb7c
The previous cleanup step found nothing to delete under C:\w\.cache\act (zero "Removing stale target dir" lines), meaning either per-job isolation hides sibling runs' directories, or the actual disk consumer is something else entirely (rustup toolchains, cargo registry cache, etc.). List what's really under C:\w and its sizes before guessing at a fix a third time. |
||
| .agents/skills | ||
| .bork | ||
| .cargo | ||
| .claude | ||
| .codex | ||
| .config | ||
| .forgejo/workflows | ||
| .github | ||
| .vscode | ||
| agent-tests | ||
| agents | ||
| app | ||
| command-signatures-v2/js | ||
| committee-tests | ||
| crates | ||
| docker | ||
| docs | ||
| images | ||
| resources | ||
| script | ||
| specs | ||
| tools | ||
| vendor | ||
| .borkindexingignore | ||
| .clippy.toml | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .mcp.json | ||
| .PSScriptAnalyzerSettings.psd1 | ||
| .rustfmt.toml | ||
| 3RDPARTYAGENTS-DESIGN.md | ||
| about.hbs | ||
| about.toml | ||
| ACCOUNT-DESIGN.md | ||
| ACCOUNTS.md | ||
| AGENTS.md | ||
| BORK-AGENT.md | ||
| BORK-KNOWLEDGE.md | ||
| BORKDRIVE-DESIGN.md | ||
| cargo-bundle | ||
| cargo-bundle.zip | ||
| Cargo.lock | ||
| Cargo.toml | ||
| deny.toml | ||
| diesel.toml | ||
| FAQ.md | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE-AGPL | ||
| LICENSE-MIT | ||
| MISERYMODE-DESIGN.md | ||
| MULTIAGENT-DESIGN.md | ||
| pr_diff.txt | ||
| PSScriptAnalyzerCustomRules.psm1 | ||
| README.md | ||
| RENDER-DESIGN.md | ||
| review.json | ||
| rust-toolchain.toml | ||
| SECURITY.md | ||
| SERVER-DESIGN.md | ||
| SINGLEAGENT-DESIGN.md | ||
| skills-lock.json | ||
| TXTFX-DESIGN.md | ||
Website · Code · Agents · Terminal · Drive · Docs · How Bork Works
Note
OpenAI is the founding sponsor of the new, open-source Bork repository, and the new agentic management workflows are powered by GPT models.
About
Bork is an agentic development environment, born out of the terminal. Use Bork's built-in coding agent, or bring your own CLI agent (Claude Code, Codex, Gemini CLI, and others).
Installation
You can download Bork and read our docs for platform-specific instructions.
Bork Contributions Overview Dashboard
Explore build.bork.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 Bork 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
Bork's UI framework (the borkui_core and borkui crates) are licensed under the MIT license.
The rest of the code in this repository is licensed under the AGPL v3.
Open Source & Contributing
Bork'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 Bork team in the
#oss-contributorsSlack channel — a good place for ad-hoc questions, design discussion, and pairing with maintainers. New here? Join the Bork 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 Bork 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 Bork from source:
./script/bootstrap # platform-specific setup
./script/run # build and run Bork
./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
- See our docs for a comprehensive guide to Bork's features.
- Join our Slack Community to connect with other users and get help from the Bork team — contributors hang out in
#oss-contributors. - Try our Preview build to test the latest experimental features.
- 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. Bork follows the Code of Conduct. To report violations, email bork-coc at bork.baby.
Open Source Dependencies
We'd like to call out a few of the open source dependencies that have helped Bork to get off the ground: