[AgentOps][BugFix] Make sure the development mode auto load mechanism works#474
Merged
XinweiHe merged 1 commit intopivot/agentopsfrom Mar 2, 2026
Merged
Conversation
Greptile SummaryThis PR enables development mode hot-reload by configuring the Key Changes:
Implementation Notes:
Confidence Score: 4/5
Important Files Changed
Last reviewed commit: 409c187 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fix development mode auto-reload mechanism and resolve TypeScript build issues across the monorepo.
Type of Change
Details
1. Core Package: Switch to Bundler Mode
frontend/packages/coremoduleResolutionfromNodeNext→bundlerin tsconfigpackage.jsonexports to usesrc/directly instead ofdist/.jsextensions from all imports (bundler mode handles resolution)This enables hot-reload for the core package during development — changes are picked up immediately without rebuilding.
2. Agent Package: Fix TypeBox Type Resolution
frontend/packages/agentimport { Type } from "@sinclair/typebox"→import { Type } from "@mariozechner/pi-ai"in 5 tool files@sinclair/typeboxdependencyWhy:
pi-agent-coreexportsAgentTool<TSchema>whereTSchemacomes frompi-ai's typebox. ImportingTypedirectly from a separate@sinclair/typeboxdependency caused TypeScript to see two differentTSchematypes (even though same version), failingtscwith[Kind] symbol missingerrors. Usingpi-ai's re-export ensures type identity.3. Billing Worker: Use Dev Mode
tmux_tools/launcher.pypnpm build && node dist/index.js→pnpm devVerification
Both consumer packages now build successfully:
Files Changed
frontend/packages/core/package.jsonsrc/frontend/packages/core/tsconfig.jsonmoduleResolution: bundlerfrontend/packages/core/src/*.ts.jsextensionsfrontend/packages/agent/package.json@sinclair/typeboxdepfrontend/packages/agent/src/tools/*.tsTypefrompi-aitmux_tools/launcher.pypnpm devfor Billing WorkerChecklist