Skip to content

security(core): keep the agent from naming a path on the host - #282

Open
arthware-dev wants to merge 1 commit into
mainfrom
fix/agent-vault-path
Open

arthware-dev wants to merge 1 commit into
mainfrom
fix/agent-vault-path

Conversation

@arthware-dev

@arthware-dev arthware-dev commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • The core API runs on the host and passes the agent's command lines to stack. --vault <path> (memory search, ask, person show), --file <path> (memory capture) and messages upload <path> let a prompt in an email make the agent read, file or post any file on the Mac.
  • The API now refuses such a line before it runs. The agent's own tools never send one.

The core API runs on the host and passes the agent's command lines to
`stack`. `memory search`, `memory ask` and `memory person show` take
`--vault <path>`, `memory capture` takes `--file <path>`, and
`messages upload` takes a path when an admin allows `messages`. A
prompt in an email or a web page could make the agent read markdown
anywhere on the Mac, or file or post any file and read it there.

The API now refuses a line that names a path on the host before
anything runs. The agent's own tools never send one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant