summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorNate Sesti <sestinj@gmail.com>2023-07-24 19:19:33 -0700
committerNate Sesti <sestinj@gmail.com>2023-07-24 19:19:33 -0700
commit000e9c0735c50bd6cb63866441d7f73083665902 (patch)
treee721ae8223e4683f12522861d82036ead1f7993d /docs
parent0672fa836c9e2b242fbc530ebdb645192c4b0590 (diff)
downloadsncontinue-000e9c0735c50bd6cb63866441d7f73083665902.tar.gz
sncontinue-000e9c0735c50bd6cb63866441d7f73083665902.tar.bz2
sncontinue-000e9c0735c50bd6cb63866441d7f73083665902.zip
telemetry refactoring and switch config.json->py
Diffstat (limited to 'docs')
-rw-r--r--docs/docs/concepts/policy.md2
-rw-r--r--docs/docs/telemetry.md11
2 files changed, 7 insertions, 6 deletions
diff --git a/docs/docs/concepts/policy.md b/docs/docs/concepts/policy.md
index 3c40115d..e08458d8 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/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.
+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.py` 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 5d2fedf1..de3b9e11 100644
--- a/docs/docs/telemetry.md
+++ b/docs/docs/telemetry.md
@@ -14,12 +14,13 @@ We track
## How to opt out
-There is a `.continue` directory, which contains a `config.json` file that looks like this:
+There is a `.continue` directory, which contains a `config.py` file that looks like this:
-```json
-{
- "allow_anonymous_telemetry": true
-}
+```python
+config = ContinueConfig(
+ allow_anonymous_telemetry=True,
+ ...
+)
```
You can turn off anonymous telemetry by changing the value of `allow_anonymous_telemetry` to `false`.