mirror of
https://github.com/zed-industries/zed.git
synced 2026-05-28 09:34:29 +00:00
original uri https://github.com/zed-industries/zed
https://zed.dev
63ea24259a
## Summary - Adds a "Rules Hygiene" section to `.rules` after the existing Build Guidelines section - Establishes clear guidelines for when/how AI agents should propose `.rules` changes - Adds a "Crash Investigation" section with reference to `script/crash-to-prompt` and other crash tooling ## What's in the Rules Hygiene section **After any agentic session:** Agents should include a "Suggested .rules additions" heading in their PR description if they discover non-obvious patterns. Reviewers decide what gets merged. **High bar for new rules:** Editing existing rules is always welcome. New rules must be (1) non-obvious, (2) repeatedly encountered, and (3) specific enough to act on. Single-crate rules go in that crate's `.rules`. **No drive-by additions:** Rules emerge from validated patterns through a 3-step workflow: agent notes pattern → team validates → dedicated commit. ## Context Part of the Background Agent Pipeline initiative (BIZOPS-801). As we scale automated crash investigation, we need guardrails to prevent `.rules` bloat from agent sessions. ## Test plan - [ ] Open a test agent session and confirm it sees the Rules Hygiene guidance - [ ] Verify the guidance is clear enough to follow without additional context 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com> |
||
|---|---|---|
| .cargo | ||
| .cloudflare | ||
| .config | ||
| .factory/prompts | ||
| .github | ||
| .zed | ||
| assets | ||
| ci | ||
| crates | ||
| docs | ||
| extensions | ||
| legal | ||
| nix | ||
| script | ||
| tooling | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .mailmap | ||
| .prettierrc | ||
| .rules | ||
| AGENTS.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CLAUDE.md | ||
| clippy.toml | ||
| CODE_OF_CONDUCT.md | ||
| compose.yml | ||
| CONTRIBUTING.md | ||
| debug.plist | ||
| default.nix | ||
| Dockerfile-collab | ||
| Dockerfile-collab.dockerignore | ||
| Dockerfile-cross.dockerignore | ||
| Dockerfile-distros | ||
| Dockerfile-distros.dockerignore | ||
| flake.lock | ||
| flake.nix | ||
| GEMINI.md | ||
| LICENSE-AGPL | ||
| LICENSE-APACHE | ||
| LICENSE-GPL | ||
| livekit.yaml | ||
| lychee.toml | ||
| Procfile | ||
| Procfile.all | ||
| Procfile.web | ||
| README.md | ||
| renovate.json | ||
| REVIEWERS.conl | ||
| rust-toolchain.toml | ||
| rustfmt.toml | ||
| shell.nix | ||
| typos.toml | ||
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.
Sponsorship
Zed is developed by Zed Industries, Inc., a for-profit company.
If you’d like to financially support the project, you can do so via GitHub Sponsors. Sponsorships go directly to Zed Industries and are used as general company revenue. There are no perks or entitlements associated with sponsorship.