/docs/how-continue-works

Thoughts

• Bullets are kinda cool (though I might change it to numbers at the highest level to know what is a step and what is not and maybe even use letters for sub-steps in bullets, numbers, or letters) -- the last line should only have one bullet though
• Another alternative would be to use toggles like Notion (where you get the high level summary and then can open it up to see the substeps)
• If we do get rid of the other boxes, then I would move the gradient border to the remaining text input box
• Making sure things within the transparent area are centered is key imo (e.g. input box is not rn)
• Having the colorful border around that area even width would likely improve things
• changing the Continue button logo and text to the same as the website would give many more people the "aha moment" behind our name
• I think commands should be formatted like markdown (maybe variable names and file names too)
• Stack traces should probably be formatted

# like markdown too
Traceback (most recent call last):
  File ...

• Not sure what those dark grey pixels are near the bottom left, but those should not be there if they are
• I think "Ran command: x" can just be "Ran x"
• In front of the traceback, I think there should be something like "Encountered error"
• I might suggest we put the word "I" in front of things to make it all from the developers point of view, so "I ran this", "I encountered this error", "I changed second"m etc. (to make it clear that Continue autocompletes their thoughts and they are responsible for any code that was written automatically)
• / commands would be nice to kick off different plug-ins
• Lines should never be cut off (like they are now) and we should not wrap any text

_{From SyncLinear.com | CON-19}

/docs/install

/docs/concepts/

null

_CON-15

/docs/walkthroughs/create-a-recipe

null

_CON-22

null

_CON-23

null

_CON-28

null

_CON-30

Try this in PostHog, I think it can be really good.

_{From SyncLinear.com | CON-20}

/docs/walkthroughs/use-a-recipe

I want some basic step or SDK methods for the fundamental things:
Create or delete a directory / file step
Read a directory / file step
Write to a file step
Run any command step
Retrieve stdout / stderr step
Save state for later step
Retrieve state saved for later step
Edit state saved for later step
Retrieve previous steps history
Call model with context + instructions step

/docs/walkthroughs/use-the-gui

null

_CON-14

I think you can preload an image, that or use the "quickstart" option. Preload with the continue extension already installed if possible.

_{From SyncLinear.com | CON-25}

null

_CON-18

https://cla-assistant.io/

/docs/getting-started

/docs/concepts/sdk

1. We should not depend on a native VS code input for users to add their API key
2. It should not block the reveal of the Continue GUI like it does now (input should probably show up in the Continue GUI)
3. The API key should be stored in some sort of config / settings file that is easily accessible by the user (where they can adjust what model is used and other things going forward)

https://bookface.ycombinator.com/knowledge/9X-two-sentence-description

_CON-21

Nate will set this up, then potentially hand off to Ty to implement a few metrics where he wants.

We should reintroduce anonymous telemetry, so we can see when people are using it and how we are using it once we start sharing recipes

https://www.notion.so/dlthub/Continue-dltHub-Design-Partnership-Technical-Proposal-d45ceb663a8f4fa8863fa0719bd0a801

_CON-17

null

_CON-26

Our product is very annoying to use if too slow.

As I have ideas abt prompt engineering, I'll drop here.

• Note that length of prompt DOES NOT affect completion time, all that matters is the number of tokens that are outputted by the model. So good to write nice preamble.
• One idea: check line-by-line or function-by-func and ask "Does this need to be edited? If so, output the edited version, if not output 'No edit needed'."
• Make sure you can get it to output a format that can be reliably parsed. I often use the triple-tick to indicate code, but JSON or XML or custom also an option.

null

_CON-29

/docs/walkthroughs/share-a-recipe

null

_CON-11

Includes:

• Docusaurus docs (and find a simple way to host this) (Ty mostly)
• Great README at the root of main folder, extension, and continuedev (Nate mostly)
• READMEs sprinkled throughout where necessary
• Top-level README should have instructions and download link for the VS Code extension.
• README that will show on PyPI (https://pypi.org/project/continuedev/), which is in root of continuedev directory

Webpack requires so many polyfills that it just seems like the wrong solution. Try esbuild: https://code.visualstudio.com/api/working-with-extensions/bundling-extension

_CON-24

null

_CON-27

null

_CON-16

1. Make it disappear
2. Make styling fit brand
3. Make it more clear that you should enter your email