summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/docs/concepts/continue-json.md4
-rw-r--r--docs/docs/concepts/policy.md2
-rw-r--r--docs/docs/telemetry.md4
3 files changed, 5 insertions, 5 deletions
diff --git a/docs/docs/concepts/continue-json.md b/docs/docs/concepts/continue-json.md
index 7227f660..f176bdff 100644
--- a/docs/docs/concepts/continue-json.md
+++ b/docs/docs/concepts/continue-json.md
@@ -1,3 +1,3 @@
-# continue.json
+# config.json
-**TODO: Need to explain this** \ No newline at end of file
+**TODO: Need to explain this**
diff --git a/docs/docs/concepts/policy.md b/docs/docs/concepts/policy.md
index ea515673..3c40115d 100644
--- a/docs/docs/concepts/policy.md
+++ b/docs/docs/concepts/policy.md
@@ -8,7 +8,7 @@ A **policy** is decides what step to run next and is associated with a [autopilo
## Details
-A relic of my original plan that ended up being the place to define slash commands, the command run on startup, and other weird stuff that you might want to inject after certain other steps. This may be the place where "hooks" turn out to be implemented. Much of this may be configurable through `continue.json/yaml` config file (this is where steps that run on GUI opening are currently configured.). Simply takes the history and returns a single step to run next. Can return None if no step to take next. Then user input will kick it off again eventually. Autopilot has a single policy that it follows, so definitely a global/user-configurable type of thing.
+A relic of my original plan that ended up being the place to define slash commands, the command run on startup, and other weird stuff that you might want to inject after certain other steps. This may be the place where "hooks" turn out to be implemented. Much of this may be configurable through `.continue/config.json/yaml` config file (this is where steps that run on GUI opening are currently configured.). Simply takes the history and returns a single step to run next. Can return None if no step to take next. Then user input will kick it off again eventually. Autopilot has a single policy that it follows, so definitely a global/user-configurable type of thing.
- The Policy is where slash commands are defined
- The Policy is a global thing, so probably something we'll want to make user-configurable if we don't significantly change it
diff --git a/docs/docs/telemetry.md b/docs/docs/telemetry.md
index 47f5a171..ca1fb641 100644
--- a/docs/docs/telemetry.md
+++ b/docs/docs/telemetry.md
@@ -14,10 +14,10 @@ We track the following...
**TODO: Define where the root of your workspace**
-Create a `continue.json` file in the root of your workspace and add the following:
+Create a `.continue/config.json` file in the root of your workspace and add the following:
```json
{
"allow_anonymous_telemetry": false
}
-``` \ No newline at end of file
+```