Run a FlareDeck agent on your own machine: it picks up cards assigned to it, works each one in a checkout of its own, and reports back on the card.
Flagged as AI-agent capability risk
Allowed by default with warning: agent-facing configuration or capability changes need review before use.
AI security review
scanned · by lpm-firewall-ai
This version provides a broad remote shell capability that is enabled by default and controlled by the workspace manager, with a local opt-out. The manager-request trigger and FlareDeck response fit the product’s operation, so the source does not establish malicious activity, but the default capability warrants a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
A live FlareDeck `exec` event carrying a request that the manager’s API claims.
Impact
Commands run with the agent user’s permissions and can access or modify that user’s files and environment. The capability is broader than card processing and may surprise users who have not disabled it.
Mechanism
The handler passes the claimed command to `bash -lc`, runs it in the agent’s configured repository directory, and returns its output to FlareDeck. A local `remote off` setting refuses execution.
382 { type: 'text', text: `This is the screen at ${viewport.width}×${viewport.height}. Judge only what is plain to see; never give a size in pixels.${takeStuckNote()}` },
// npx puts npm[redacted] in the environment, and the environment beats the config FILE
32// we just wrote — which is why `npm config set prefix` appeared to work and the install
⋯
58functionshellProfile() {
59const home = homedir();
60const shell = process.env['SHELL'] ?? '';
61const candidates = shell.includes('zsh')
62 ? ['.zshrc', '.zprofile', '.profile']
63 : ['.bashrc', '.bash_profile', '.profile'];
'never'
35});
⋯
44}
45/** `https://github.com/Owner/Repo(.git)` → `owner__repo`: the clone's folder name. */