Extension API: expose active tools as executable objects, not just names

[pandysp]

What do you want to change?

Add getActiveExecutableTools(): AgentTool[] to the extension API, the counterpart of getActiveTools() (which returns only names). A shallow copy of the live active set.

Why?

I'm building an extension that runs observers alongside the agent. Each forks the live session as the agent works and can act with the agent's own tools.

In my extension the observers fork the live session (vs. subagents that have full toolset in their own sessions), and I want them to use the tools from that main session. I can register new tools and list the active ones by name, but there's no runnable handle to them, so an observer can see a tool and still not run it.

How? (optional)

Return agent.state.tools.slice() (the active set, so built-ins are included), wired alongside getActiveTools. Implemented locally with a test, happy to PR if approved.

[github-actions]

This issue was auto-closed. All issues from new contributors are auto-closed by default.

Maintainers review auto-closed issues daily and reopen worthwhile ones. Issues that do not meet the quality bar in CONTRIBUTING.md will not be reopened or receive a reply.

If a maintainer replies lgtmi on one of your issues, your future issues will stay open. If a maintainer replies lgtm, your future issues and PRs will stay open.

See CONTRIBUTING.md.

[pandysp]

Quick clarification on the ticket. It's AI drafted but heavily edited by me. I believe the feature gap is real not AI hallucinated.

Let me just show the thing I'm actually blocked on. My extension (pi-hydra) runs observers that replay the live session and act with the agent's own tools. Today I can only hand an observer the built-in tools because those are the only ones I can construct myself:

// today: I can only construct the built-ins
const tools = [
  createReadTool(cwd), createBashTool(cwd), createEditTool(cwd), createWriteTool(cwd),
  createGrepTool(cwd), createFindTool(cwd), createLsTool(cwd),
];

(the real thing: https://github.com/pandysp/pi-hydra/blob/fe42630de1a67b06eff23ea518172a67b63fda3c/index.ts#L749-L776)

With the accessor it's whatever is actually active in the session:

const tools = pi.getActiveExecutableTools();

And this isn't just convenience. Even hardcoding can't reach another extension's tools or MCP tools because I can't know ahead of time what they are. I can see their names (getActiveTools()) but a name isn't runnable and I have no factory for a tool I didn't write.

I can open a PR with a throwaway reference implementation that I am running in my local fork if that helps.