Bundle the engine launcher into source-built debug apps#8
Open
jakimoai wants to merge 1 commit into
Open
Conversation
This was referenced Jul 11, 2026
jakimoai
marked this pull request as ready for review
July 12, 2026 05:24
jjang-ai
pushed a commit
that referenced
this pull request
Jul 14, 2026
NetworkHostEntry already carried .signing and .shares (populated by
netexec/nxc ingestion) but the row rendered only ip/hostname/os/status.
The signing state ("signed", "not required", "required") and enumerated
share list often determine the next attack path, so hiding them behind
Copy-only context menus made critical evidence undiscoverable.
Added an info button per host row that opens NetworkHostDetailSheet with:
- Header: ip + optional hostname + status pill (Pwn3d! red / else green)
- Metadata grid: ip, hostname, os, smb signing, shares, status, likely tool
- Likely-tool heuristic: snmpwalk for status=="snmp"; netexec/nxc when
signing or shares populated; otherwise nmap + netexec/nxc
- Scrollable selectable raw-output tail from ResultsStore.rawResults
matched by tool name
Same shape as ReconResultDetailSheet (37ef439). Web #11 and Creds #7 land
next iter.
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
1 participant
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
Bundles
ExploitBotEngineinto source-built debug apps so the app resolves the same resource-based launcher layout used by distributed builds.Problem
EngineManagerchecks the app resources first, butscript/build_and_run.shdid not copy the engine into the generated app bundle. Source builds outside the hard-coded fallback location could reportEngine launch script not found.Root Cause
The runtime launcher supported a bundled resource path while the source debug build omitted those resources.
Fix
ExploitBotEngineintoContents/Resources/ExploitBotEngineduring source debug builds.No model generation, scheduler, cache, parser, or chat UI behavior changes.
Why This Shape
The build now satisfies the launcher contract already implemented by
EngineManager, without adding another source-checkout path assumption.App Proof
ExploitBotEngine/launch.pyvmlx_engine/server.pyStarting...on an allocated portThe process was stopped immediately after the launch-boundary capture to avoid competing with another active local runtime session. Model load and generation are outside this packaging-only change.
Visual Proof
The source-built app's Engine settings view was captured in
Starting...state after the bundled launcher resolved and the process spawned, with no launcher-not-found error.Follow-up / Out of Scope
Related PRs
Tests
bash -n script/build_and_run.sh script/package_release.sh./script/build_and_run.sh --build-only