add new course on Foundry Toolkit#10027
Conversation
|
Bonjou |
|
|
||
| This is where most implementation work happens. You will use it to move from model exploration to agent development and then into validation. As your project grows, this section becomes a practical day-to-day control center. | ||
|
|
||
| For example, a common loop is: open Model Catalog, test a prompt in Playground, then inspect behavior in Agent Inspector without leaving the same extension area. |
There was a problem hiding this comment.
I don't think the suggested path actually makes sense, as you don't usually move from playground to agent inspector. Agent inspector is more for pro-code agent debugging. Can we just skip this sentence?
| - **Build**: Agent creation, Agent Inspector, hosted agent management, and playground workflows. | ||
| - **Monitor**: Tracing, evaluations against expected behavior, and model profiling. | ||
|
|
||
| After building and monitoring, you still need support and feedback channels to keep improving. |
There was a problem hiding this comment.
I suggest rephrasing this as follows: "As you build and test your soultion, you might need support..."
| Once you've installed Foundry Toolkit, you should know the layout and where to find the tools you need. The extension is organized into three main sections: My Resources, Developer Tools, and Feedback. | ||
|
|
||
| Once Foundry Toolkit is installed, the UI is organized into sections that mirror how teams actually build. Learning this layout early saves discovery time and helps new teammates get oriented much faster. | ||
|
|
There was a problem hiding this comment.
I think those 2 sentences might be merged into one, to avoid redundancy.
|
|
||
| 1. Open Foundry Toolkit and click into My Resources. | ||
| 2. Expand one available section, even if it is currently sparse. | ||
| 3. Say out loud what you can see now that you could not see five minutes ago. |
There was a problem hiding this comment.
Not sure what you mean here - you see more stuffs under my resources just if you create models/agents or connect to an existing Foundry project. Since they are in the set up phase, they shouldn't be able to see much
|
|
||
| - **Visual Studio Code**: Installed and updated so extension workflows and command surfaces are available. | ||
| - **Foundry Toolkit extension**: Installed and visible in the activity bar. | ||
| - **GitHub Copilot**: Enabled for recommendation-driven model shortlisting. |
There was a problem hiding this comment.
I don't think this statement really makes sense, as there's no additional set up required to enable GitHub Copilot for recommendation-driven model shortlisting (in addition to having the Toolkit installed).
| See the "Evaluation" tab in the image below. Select that. | ||
|
|
||
|  | ||
|
|
There was a problem hiding this comment.
Why we are showcasing a different example wrt to the social media agent in those screenshot? Ideally we should stick with the same use case IMHO
|
|
||
| 2. Select to generate a dataset by clicking the top left button. | ||
|
|
||
| You should first be met with a modal that shows you a prompt template for generating a dataset. Confirm the prompt and select to generate a dataset. This will create a JSONL file with test rows that you can use for evaluation. |
There was a problem hiding this comment.
I guess there's a typo here -> 'modal' instead of 'model'
carlotta94c
left a comment
carlotta94c
left a comment
There was a problem hiding this comment.
Reviewing the rest of the chapters
3 participants
No description provided.