stackwise
stackwise copied to clipboard
The open source AI app collection
CI pipeline is always red no matter what. For example https://github.com/stackwiseai/stackwise/pull/65 Success criteria: When creating a pr, tests run on the stack created ( and nothing more)
Description of feature: When on a line, speak and get your stack created
Problem: It's hard to know what a stack does just from one look. Solution: have an input and output folder that record input and output of a stack when running...
TODO: add no implicit any and maybe other tsconfing rules
Currently the stacks are not linked to the vscode extension. Success criteria: - adding a stack and merging it to the main repo affects our vscode extension (hopefully positively)
Everything that doesn't use the vscode package should go on the server side, in order to get a light client and put all the logic in the server. You'll get...
The index.test.txt is very redundant. We use it to know in which context the stack was collapsed. TODO: Try to find something that gets built on Pull requests, this way...
When running this brief: ``` stack( "Call gpt-4 using the streaming endpoint to answer my question and text to speech the voice in real time", {in: "What is the meaning...
Success criteria: - all the calls made to pinecone should be made to supabase - the end to end tests are all passing
Ran into a minor bug (or not), while working on: https://github.com/stackwiseai/stackwise/pull/28. Basically, passing a callback function inside `in`. Do let me know if this should be supported by Stackwise or...