Some Sidekick quickstart edits. #281
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| ### Method 1: Via curl | ||
| > TODO(matt): Figure out the right invocation for this. |
There was a problem hiding this comment.
See https://github.com/fixie-ai/fixie/blob/5452e48b739f9941e3facabaad9a2f1d4f59f49c/src/generic-sidekick-frontend/lib/fixie-api.ts for an example of how this API is used.
I feel pretty strongly that if we do this, we should remove the That said, branch in general is a big improvement over what we have live, so cleaning it up + merging sounds good. |
|
|
||
| Note: you can also access your agent directly at: | ||
| You can also access your agent directly at: |
There was a problem hiding this comment.
This section feels redundant. I don't think we need to both provide a direct link to the dev console, and also tell people how to go to the front door of the dev console and then click through it.
| TODO could we just include a simple web page in the template code that can be served up locally? | ||
|
|
||
| _TODO Matt: need to figure out if we add this or not_ | ||
| > TODO(matt): Figure out what the right thing to do here is. |
There was a problem hiding this comment.
I would punt on this for now
There was a problem hiding this comment.
ok removing the part about embedding for now. opened issue #284 to track the work for doing this in future.
Co-authored-by: Nick Heiner <[email protected]>
|
i folded all these changes in via a diff PR |
Made some proposed edits to the Sidekick quickstart. Definitely a few things we need to chase down in the next couple of days, but all doable.
I recommend we just push these changes to the live docs site and work off of
mainsince I don't think it gets so much traffic that people are gonna get confused if we start rolling things out.