diff --git a/crates/copilot/readme.md b/crates/copilot/readme.md
deleted file mode 100644
index a91608197006fa2bd0b2ac2b90c5d36548060063..0000000000000000000000000000000000000000
--- a/crates/copilot/readme.md
+++ /dev/null
@@ -1,21 +0,0 @@
-Basic idea:
-
-Run the `copilot-node-server` as an LSP
-Reuse our LSP code to use it
-
-Issues:
-- Re-use our github authentication for copilot - ??
-- Integrate Copilot suggestions with `SuggestionMap`
-
-
-
-THE PLAN:
-- Copilot crate.
-- Instantiated with a project / listens to them
-- Listens to events from the project about adding worktrees
-- Manages the copilot language servers per worktree
-- Editor <-?-> Copilot
-
-
-From anotonio in Slack:
-- soooo regarding copilot i was thinking… if it doesn’t really behave like a language server (but they implemented like that because of the protocol, etc.), it might be nice to just have a singleton that is not even set when we’re signed out. when we sign in, we set the global. then, the editor can access the global (e.g. cx.global::<Option<Copilot>>) after typing some character (and with some debouncing mechanism). the Copilot struct could hold a lsp::LanguageServer and then our job is to write an adapter that can then be used to start the language server, but it’s kinda orthogonal to the language servers we store in the project. what do you think?
diff --git a/crates/settings/src/settings.rs b/crates/settings/src/settings.rs
index 2e087dd26080a593830815f8aae93a91eb168200..5825e48d5a6e2019027237341aa1ad6c6f1db2b4 100644
--- a/crates/settings/src/settings.rs
+++ b/crates/settings/src/settings.rs
@@ -945,7 +945,6 @@ fn write_settings_key(settings_content: &mut String, key_path: &[&str], new_valu
                 settings_content.insert_str(first_key_start, &content);
             }
         } else {
-            dbg!("here???");
             new_value = serde_json::json!({ new_key.to_string(): new_value });
             let indent_prefix_len = 4 * depth;
             let new_val = to_pretty_json(&new_value, 4, indent_prefix_len);