JavaScript can run inside Obsidian’s trusted application context
Source references: 2The Skill explicitly permits `obsidian eval` to execute code in the application context. The shown example only counts files, but the interface is not stated to be restricted to that read-only expression; risk depends on code the agent later constructs.
Unreviewed code or code influenced by untrusted content could use objects exposed by Obsidian to read or alter vault data, subject to the permissions available in that application context.
This is an active developer-command instruction, not a warning or negation: it permits JavaScript execution in Obsidian's application context. The shown expression only counts files and does not establish harmful execution, but the interface expands the authority and impact of subsequently generated code. Users can restrict eval to reviewed, read-only expressions and require separate approval for code that mutates data.
Run JavaScript in the app context:```bashobsidian eval code="app.vault.getFiles().length"```Show 1 other places
Run `obsidian help` to see additional developer commands including CDP and debugger controls.