Feature request: Support workingDirectory in settings.json

Resolved 💬 2 comments Opened Jun 16, 2026 by jkyoung7-stack Closed Jun 19, 2026

Summary

Currently, Claude Code's working directory is determined solely by the directory from which claude is invoked. Other AI coding agents (e.g., Google Antigravity, OpenCode) support setting a default working directory via their settings.json config files.

Request

Add a workingDirectory field to ~/.claude/settings.json so users can configure a persistent default working directory without relying on shell aliases.

Example config:

{
  "theme": "dark-ansi",
  "workingDirectory": "/home/user/.dev"
}

Use Case

Multi-agent development environments where several AI agents (Claude Code, Antigravity, Codex, etc.) collaborate on a shared project directory. Each agent should consistently start in the same workspace without requiring shell alias workarounds.

Current Workaround

Users must add a shell alias to .bashrc:

alias claude='cd /path/to/project && claude'

This is less clean than native config support and inconsistent with how other agents handle this.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗