Skip to content

fix(session): default working directory to /tmp when none is set - #19

Open
gpasquero wants to merge 1 commit into
formulahendry:mainfrom
gpasquero:fix/default-working-directory
Open

gpasquero wants to merge 1 commit into
formulahendry:mainfrom
gpasquero:fix/default-working-directory

Conversation

@gpasquero

Copy link
Copy Markdown

Problem

Starting a session with an empty Working Directory field fails fast with "Please enter a working directory (absolute path on the agent's machine)." For remote (WebSocket) agents the cwd is interpreted on the agent's host, not the client device, so forcing the user to type a path before they can connect is often unnecessary friction — especially on mobile/web where there's no folder picker.

Change

  • Prefill the Working Directory field with a POSIX default (/tmp).
  • Fall back to that default in handleNewSession when the field is left empty, instead of erroring.
  • The existing absolute-path validation still applies, and desktop users can still override via the native folder picker.

Scoped to src/App.vue.

Testing

  • npx vue-tsc --noEmit passes.
  • Web build: creating a session against a remote agent with the field left at its default connects using /tmp instead of showing the error.

The New Session flow rejected an empty working directory with a 'Please
enter a working directory' error. For remote agents the cwd is interpreted
on the agent's host, so requiring the user to type one before connecting is
often unnecessary friction. Prefill the field with a POSIX default (/tmp)
and fall back to it when the field is left empty; the absolute-path
validation still applies and desktop users can still override via the
folder picker.
gpasquero pushed a commit to gpasquero/acp-ui that referenced this pull request Aug 26, 2026
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