First stab at JS-based CLI for Fixie.

[mdwelsh]

The idea here is to replace the Python-based "fixie" CLI with an npm-based "fixie" CLI, which will allow one to create and manage Sidekicks and Corpora. This way an AI.JSX developer need not have a Python environment set up. It also provides a JS-based FixieClient class for interacting with the Fixie platform APIs programmatically.

This version only has the Corpus-related commands, we will need to port over the logic from the Python-based "fixie deploy" command for AI.JSX Sidekick deployment to JS as well.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ai-jsx-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 28, 2023 11:08pm
ai-jsx-nextjs-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 28, 2023 11:08pm
ai-jsx-tutorial-nextjs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 28, 2023 11:08pm

[NickHeiner]

For reference, here's the Codeshot fixie-sdk TS feature branch: https://github.com/fixie-ai/fixie-sdk/tree/feature-ts.

[NickHeiner]

This command took 37 seconds to run, which surprised me:

yarn workspace fixie start corpus create help-scout -u https://beta.fixie.ai
Created corpus:
{
  "corpus": {
    "corpusId": "8d3fff4b-09e0-4ff3-901a-a4c517bee019",
    "created": "2023-08-28T13:07:06.821890Z",
    "modified": "2023-08-28T13:07:07.244390Z",
    "name": "help-scout"
  }
}⏎                                                                                                                                                                                                                                                                                                                                                                                                                          

I think that's just because the service had to spin up, and thus this isn't worth worrying about.

[NickHeiner]

I used this to make a Help Scout corpus: 8d3fff4b-09e0-4ff3-901a-a4c517bee019. We'll see how it does. 😄

[NickHeiner]

Is there a single command I can run to get corpus status? (e.g. is it ready to query)

[mdwelsh]

Thanks for the comments - PTAL

[mdwelsh]

I think that's just because the service had to spin up, and thus this isn't worth worrying about.

Yep, I'm fixing this.

[mdwelsh]

Is there a single command I can run to get corpus status? (e.g. is it ready to query)

Not yet but I will add that to the backend.

[NickHeiner]

[mdwelsh]


Hey, the error message is correct! "Missing argument query" on your first command line is exactly right: an argument is not the same thing as an option!