welcome to flo!

flo uses a langchain functions agent to catch errors thrown by the next.js development process. it then attempts to solve these errors or at least find out what's wrong by scanning your codebase for the faulty code.

since flo "lives" in your codebase, it doesn't need you to provide any context. it also doesn't need you to copy + paste a super long error message anywhere, flo catches your erros and parses them on it's own!

enough intros, let's start catching some errors :)

usage

configuration

so, once you've installed the flo extension you're gonna need to configure it. you can do this by opening the command palette and searching for the configure flo command. you'll then be prompted to add your openai api key. this key is never written to a database. we use vscode's secret storage and do not have access to your keys. if you don't have an openai key, don't worry - the extension will open the browser for you so that you can get one.

optionally you can further configure flo by enabling the agent to perform web searches or power it with gpt-4-0613 rather than the gpt-3.5-turbo-0613 model: gpt-4 to enable the agent to use the gpt-4 model you can simply search for the enable GPT4 command in the cmd palette and in one click you'll have powered the agent with gpt-4. you can also disable gpt-4 by using the disable GPT4 command.

search to enable the agent to search through the web for solutions to your errors you can execute the enable search command. however, you'll need a Serp API key, so you'll be prompted to enter your key here. if you don't have one - again - the extension will open the browser so that you can get one.

debugging

once you've configured flo you'll be able to debug your next.js app. to debug you'll need to execute the run and debug with flo command from the cmd palette. this command will run your next.js app with npm run dev and then monitor it for errors.

if there's an error in your app you'll see an information message starting with the line "hmm, there seems to be an error:". then you'll have to wait a bit while flo deploys an agent to solve your error. once the agent has finished solving your error you'll see a notification with the solution that starts with the phrase "flo says:".

known issues

so the most common issue with the extension is that sometimes the agent uses the wrong file path while attempting to scan your codebase. this results in an ENOENT error that terminates the agent and prevents it from giving you a solution. this means that the extension works well with absolute file paths but may fail with some relative paths. usually you don't have to worry about this though, since the agent uses the file paths described in the error stack trace (which are usually absolute).

we catch all ENOENT errors and will display an error message telling you that flo wasn't able to read your codebase due to trying to use an invalid file path.

release notes

0.0.1

alpha extension build -- basic functionality with error solving via editor messages (next.js only)