summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorNate Sesti <sestinj@gmail.com>2023-07-26 00:26:02 -0700
committerNate Sesti <sestinj@gmail.com>2023-07-26 00:26:02 -0700
commit79a2fa634e5b5d44e13fbd49facf14a4fc3745d1 (patch)
tree0e5917d1ae3fad12e4cf459ec273593d9d5267a4 /docs
parentb759e2dbfe36b3e8873527b9736d64866da9b604 (diff)
parent2b69bf6f1fc2e06b16b718358ceed4911d6e87c3 (diff)
downloadsncontinue-79a2fa634e5b5d44e13fbd49facf14a4fc3745d1.tar.gz
sncontinue-79a2fa634e5b5d44e13fbd49facf14a4fc3745d1.tar.bz2
sncontinue-79a2fa634e5b5d44e13fbd49facf14a4fc3745d1.zip
Merge branch 'config-py' into merge-config-py-TO-main
Diffstat (limited to 'docs')
-rw-r--r--docs/docs/concepts/policy.md2
-rw-r--r--docs/docs/telemetry.md15
2 files changed, 10 insertions, 7 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..1b9a8c4b 100644
--- a/docs/docs/telemetry.md
+++ b/docs/docs/telemetry.md
@@ -9,17 +9,20 @@ Continue collects and reports **anonymous** usage information. This data is esse
We track
- the steps that are run and their parameters
-- toggling of the data collection switch
- whether you accept or reject suggestions (not the code itself)
+- the traceback when an error occurs
+
+All data is anonymous and cleaned of PII before being sent to PostHog.
## 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`.