feat: add Solana IDE control center, diagnostics, build loop, inspector, and monitor#135
Merged
nullxnothing merged 17 commits intomainfrom May 4, 2026
Merged
Conversation
# Conflicts: # src/panels/SolanaToolbox/SolanaToolbox.tsx
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
Expands the Solana Toolbox into the first real foundation for an all-in-one Solana IDE workflow.
This PR now adds five concrete surfaces and one backend diagnostics upgrade:
1. Project Control Center
2. Backend Solana project diagnostics
Anchor.tomlprograms/target/idltarget/deploydeclare_id!from program source3. Diagnose panel
4. Build / Test / Deploy panel
anchor buildanchor testcargo testpnpm test5. Transaction Inspector foundation
solana confirm -v <signature>andsolana logs.6. Program Monitor foundation
solana config getsolana program show <PROGRAM_ID>solana account <PROGRAM_ID>Why
This moves DAEMON beyond separate Solana panels and toward a connected developer loop:
Detect → Prepare → Diagnose → Build/Test → Inspect → Monitor → Debug → Ship
The implementation is intentionally practical: terminal-backed commands, read-only inspection, explicit deploy safety, and agent handoff. It avoids claiming a full production replay engine until the backend fork/replay work is actually wired.
Files changed
electron/services/SolanaDetector.tssrc/store/solanaToolbox.tssrc/panels/SolanaToolbox/ProjectControlCenter.tsxsrc/panels/SolanaToolbox/ProjectControlCenter.csssrc/panels/SolanaToolbox/ProjectDiagnosticsPanel.tsxsrc/panels/SolanaToolbox/BuildDeployPanel.tsxsrc/panels/SolanaToolbox/TransactionInspector.tsxsrc/panels/SolanaToolbox/ProgramMonitorPanel.tsxsrc/panels/SolanaToolbox/SolanaIdeWorkflow.csssrc/panels/SolanaToolbox/SolanaToolbox.tsxFollow-up work
Recommended next PRs:
solana program showoutput.Notes
I did not run the local test suite from this environment. Please run:
pnpm run typecheck pnpm testbefore merging.
Also note: the branch is currently behind
mainby 1 commit, so update/rebase before merging if GitHub requires it.