Summary
poe-code@3.0.393 runtime still forwards composable AgentRunOptions.env, but the published poe-code/agent TypeScript declaration omits the env property. This regresses the public contract released for #404 in 3.0.256.
Evidence
Runtime (dist/agent.js) forwards:
Published declaration (dist/agent.d.ts) currently defines AgentRunOptions without env.
Impact
Consumers cannot use the released per-run composable-agent environment API without a cast, module augmentation, or other local workaround. In quora/bug-analyzer, this blocks removal of serialized temporary global process.env mutation tracked by issue #24.
Requested fix
- Restore
env?: Record<string, string | undefined> to the public AgentRunOptions declaration/source type.
- Add a packaging/type-surface regression test proving the published
poe-code/agent declaration accepts per-run environment overrides, including undefined unsets.
Summary
poe-code@3.0.393runtime still forwards composableAgentRunOptions.env, but the publishedpoe-code/agentTypeScript declaration omits theenvproperty. This regresses the public contract released for #404 in3.0.256.Evidence
Runtime (
dist/agent.js) forwards:Published declaration (
dist/agent.d.ts) currently definesAgentRunOptionswithoutenv.Impact
Consumers cannot use the released per-run composable-agent environment API without a cast, module augmentation, or other local workaround. In
quora/bug-analyzer, this blocks removal of serialized temporary globalprocess.envmutation tracked by issue #24.Requested fix
env?: Record<string, string | undefined>to the publicAgentRunOptionsdeclaration/source type.poe-code/agentdeclaration accepts per-run environment overrides, includingundefinedunsets.