Fixed the harness method signatures by adding optional keys argument …

[shourikan]

…to fit the OpenAI optional key parameter and added displaying of assistance messages

Purpose

Currently the solution does break when certain action types are demanded by the computer tool from OpenAI. This is because the keys parameters is being passed from OpenAI and that breaks the generic method invocation in the code since the underlying harness methods do not expect it. Fix is to add the optional argument to the harness method signatures.

When using current solution, the assistant responses were not displayed in the interaction so conclusions were ommited for user. Fixed that by adding displaying of assistant messages.

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[X] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[shourikan]

@microsoft-github-policy-service agree