| Filename | Latest commit message | Latest commit date |
|---|---|---|
51bd1a2181
Delete the AI agent/assistant layer entirely (to be replaced by our own loop): - Removed crates: agent, agent_ui, agent_servers, acp_thread, acp_tools, skill_creator, eval_cli, eval_utils, sidebar (sidebar existed only to host the agent thread UI). ~200k LOC / ~190 files gone. - Cut all agent init + panel lifecycle + zed:// URL handlers from main.rs/zed.rs/ open_listener.rs; removed settings_ui tool-permissions page; dropped agent dev-deps and agent_sharing tests from collab/remote_server. Kept (structurally needed by retained crates, defer to later cleanup): - agent_skills (prompt_store ProjectContext + rules_to_skills_migration; also auto_update_ui, settings_ui skills page) - ai_onboarding (edit_prediction onboarding modal/upsell; language_models cloud) cargo check --workspace is GREEN (0 errors, 13 warnings). Residual: a few test-only / visual-test-gated files still ref the deleted agent crate (visual_test_runner.rs, remote_server remote_editing_tests.rs) — not in the default build; cleanup tracked for follow-up. Co-Authored-By: Claude Opus 4.8 <[email protected]> |
||
| .. | ||
| k8s | ||
| migrations | ||
| migrations.sqlite | ||
| seed | ||
| src | ||
| tests/integration | ||
| .env.toml | ||
| Cargo.toml | ||
| LICENSE-GPL | ||
| README.md | ||
| seed.default.json | ||
Zed Server
This crate is what we run at https://collab.zed.dev.
It contains our back-end logic for collaboration, to which we connect from the Zed client via a websocket after authenticating via https://zed.dev, which is a separate repo running on Vercel.
Local Development
Database setup
Before you can run the collab server locally, you'll need to set up a zed Postgres database. Follow the steps sequentially:
- Ensure you have postgres installed. If not, install with
brew install postgresql@15. - Follow the steps on Brew's formula and verify your
$PATHcontains/opt/homebrew/opt/postgresql@15/bin. - If you hadn't done it before, create the
postgresuser withcreateuser -s postgres. - You are now ready to run the
bootstrapscript:
script/bootstrap
This script will set up the zed Postgres database, and populate it with some users. It requires internet access, because it fetches some users from the GitHub API.
The script will create several admin users, who you'll sign in as by default when developing locally. The GitHub logins for the default users are specified in the seed.default.json file.
To use a different set of admin users, create crates/collab/seed.json.
{
"admins": ["yourgithubhere"],
"channels": ["zed"]
}
Testing collaborative features locally
In one terminal, run Zed's collaboration server and the livekit dev server:
foreman start
In a second terminal, run two or more instances of Zed.
script/zed-local -2
This script starts one to four instances of Zed, depending on the -2, -3 or -4 flags. Each instance will be connected to the local collab server, signed in as a different user from seed.json or seed.default.json.
Deployment
We run two instances of collab:
- Staging (https://staging-collab.zed.dev)
- Production (https://collab.zed.dev)
Both of these run on the Kubernetes cluster hosted in Digital Ocean.
Deployment is triggered by pushing to the collab-staging (or collab-production) tag in GitHub. The best way to do this is:
./script/deploy-collab staging./script/deploy-collab production
You can tell what is currently deployed with ./script/what-is-deployed.