Git and pull requests

Newen reads git and leaves the writing to the agent. It uses your git binary, so your config, hooks, attributes and LFS behave as they do in a terminal.

Changes

Ctrl+Shift+D shows the folder’s working tree against its branch, untracked files as added. Newen has no stage, commit or push buttons: ask the agent, as you would a colleague. See Changes and rewind for each request’s own record.

Pull requests

The branch bar above the message box counts the changes (View changes) and offers Create PR or Create draft PR. It asks the agent to do it: make a branch if you are on the default one, commit, push and run gh pr create, then give you the address; if the branch already has a pull request, push and give its address.

The button explains itself when it can’t: Add a GitHub remote to create a pull request, Already on the base branch — check out a feature branch first, The agent is working — wait for the turn to finish.

In Settings › Sessions › Pull requests: the Branch prefix for branches it makes, Pull request kind (Ready for review or Draft), Open pull requests in browser, and Auto-archive after PR merge.

Worktrees

Agents can make git worktrees to work apart from your checkout. Newen shows them like any folder, and Storage removes the ones nothing uses any more: clean, held by a branch or tag, and untouched for 30 days.

Your GitHub account

Settings › Accounts › GitHub connects through the GitHub CLI: Newen runs gh auth login and opens its page, and holds no credentials of its own; gh keeps them. It shows Signed in as @you, with View profile, Reconnect and Disconnect.

Without gh, Install and connect downloads the official one from GitHub into Newen’s own tools folder, and agents find it on their PATH.

Note

Snapshots for undo live in shadow repositories in Newen’s data folder. They never touch your project’s .git.