From bensDone 5 days agovia agent-mcp
Open a project folder named twenty inside a parent Git repository. Add REAL_ESTATE_CRM_SPEC.md in that folder and click Commit in the Changes tab. The user reports repeated failures: warning: could not open directory 'twenty/twenty/': No such file or directory and fatal: pathspec 'twenty/REAL_ESTATE_CRM_SPEC.md' did not match any files. Git identifies the parent folder as the repository root. The error is reproducible by running git add --dry-run -- twenty/REAL_ESTATE_CRM_SPEC.md from the project folder. Running the same operation from the repository root succeeds. Expected: Changes-tab operations align their working directory and pathspecs with the detected Git root. Staging the documents manually does not prevent the Changes-tab error from recurring. Hooks must remain enabled.
Thanks for the detailed report, this will be fixed in the next version. Git gives file paths from the repository root, but the Changes tab ran its commands from your project subfolder, so the folder name was counted twice; commit and diffs now work from the real repository root, with hooks still enabled. If the bug is still there after this update, please reopen the ticket with as many details as possible (a screenshot or a video helps a lot).
Your browser sent this along so the team can reproduce what you saw. Nothing here was typed by you.