Skip to content

docs: Adding new sections to AI Studio: Plugins#455

Merged
theekrystallee merged 11 commits intomainfrom
lindz/ai-studio-features
Mar 15, 2026
Merged

docs: Adding new sections to AI Studio: Plugins#455
theekrystallee merged 11 commits intomainfrom
lindz/ai-studio-features

Conversation

@walkerlj0
Copy link
Copy Markdown
Contributor

@walkerlj0 walkerlj0 commented Mar 6, 2026

Description:

Related issue(s):

Issue #365

Notes for reviewer:

Checklist

  • Documented (Code comments, README, etc.)
  • Tested (unit, integration, etc.)

Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
…ugins in each JS and Py agent kits

Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
@walkerlj0 walkerlj0 changed the title Adding new sections to AI Studio: Plugins, Adaptors, and Policies Adding new sections to AI Studio: Plugins Mar 12, 2026
@walkerlj0 walkerlj0 marked this pull request as ready for review March 12, 2026 22:26
@walkerlj0 walkerlj0 requested a review from a team as a code owner March 12, 2026 22:26
@theekrystallee theekrystallee changed the title Adding new sections to AI Studio: Plugins docs: Adding new sections to AI Studio: Plugins Mar 12, 2026
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
Signed-off-by: walkerlj0 <lindsay.w@hashgraph.com>
@theekrystallee theekrystallee merged commit 7bf64d1 into main Mar 15, 2026
13 of 14 checks passed
@theekrystallee theekrystallee deleted the lindz/ai-studio-features branch March 15, 2026 16:08
Comment on lines +25 to +34
```typescript
export type Tool = {
method: string;
name: string;
description: string;
parameters: z.ZodObject<any, any>;
execute: (client: Client, context: Context, params: any) => Promise<any>;
// transactionToolOutputParser and untypedQueryOutputParser can be used. If required, define a custom parser
outputParser?: (rawOutput: string) => { raw: any; humanMessage: string };
};
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@walkerlj0 just pointing out to keep it in mind that next release will change that - in order to achieve hooks support tools will have to extend BaseTool class. The Tool interface implementing tools will still work for backward compatibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants