Skip to content

feat(examples): allow disabling the pi extension via GONDOLIN_DISABLED #172

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ColonelPanics wants to merge 1 commit into
base: main
Choose a base branch
from
+4 −0
Open

feat(examples): allow disabling the pi extension via GONDOLIN_DISABLED #172

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions host/examples/pi-gondolin.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,9 @@
* Notes:
* - The VM is started on `session_start` (and lazily if a tool is used before that)
* - User `!` commands are also executed inside the VM
* - Set `GONDOLIN_DISABLED=1` to keep the extension loaded but skip VM routing,
* so pi falls back to its normal host tools (useful as an escape hatch to
* run with real system access without removing the extension)
* - Module resolution happens relative to this file, so keeping it inside the
* gondolin repo (or installing `@earendil-works/gondolin` next to it) is easiest
*/
Expand Down Expand Up @@ -162,6 +165,7 @@ function createGondolinBashOps(vm: VM, localCwd: string): BashOperations {
}

export default function (pi: ExtensionAPI) {
if (process.env.GONDOLIN_DISABLED === "1") return;
const localCwd = process.cwd();

const localRead = createReadTool(localCwd);
Expand Down