Skip to content

armgit / cogit

Public Imported from GitHub
0

Git for the intent behind agent-written code. Records what your coding agent decided and why, and links every commit to it.

fix(doctor): point a failed record send at ssh-add or a stored HTTPS login

Eren5204413433e6
diff --git a/CHANGELOG.md b/CHANGELOG.md
index e221bba..8201018 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,7 +7,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
### Fixed
- A `prepare-commit-msg` hook of your own that sets its own `trap ... EXIT` or ends with `exec` no longer drops the `Thought:` trailer: cogit now runs your lines as a child and adds the trailer once they finish. Existing hooks update on the next chat message.
-- With an SSH key that has a passphrase and no ssh-agent, the records that follow a push are no longer lost: the background send used to retry the remote every 3 seconds for 10 minutes (each a failed login) and then drop them. It now stops at the first failure and keeps them queued, and `cogit doctor` says to add the key to ssh-agent or run `cogit record-sync send` from a terminal.
+- With an SSH key that has a passphrase and no ssh-agent, the records that follow a push are no longer lost: the background send used to retry the remote every 3 seconds for 10 minutes (each a failed login) and then drop them. It now stops at the first failure and keeps them queued, and `cogit doctor` says to add the key to ssh-agent (`ssh-add`), or for HTTPS to store your login (`gh auth login`).
## [1.1.0] - 2026-11-06
### Changed
diff --git a/docs/guide/troubleshooting.md b/docs/guide/troubleshooting.md
index 58e7bff..0f7d4a9 100644
--- a/docs/guide/troubleshooting.md
+++ b/docs/guide/troubleshooting.md
@@ -25,8 +25,10 @@ cogit ties its record to commits, so it needs git. Run `git init` (or work in a
In a project that shares its record, they arrive in two steps: they send with `git push`, you
receive with `git pull`, and cogit shows them the next time it runs. If they still do not appear,
run `cogit doctor` on both machines: its record line says when a send or download failed and
-why. An SSH key that needs a passphrase has to be in `ssh-agent`, since the record is sent in the
-background where nothing can ask for it. If your project keeps its record private, nothing
+why. The record is sent in the background, where nothing can ask for a passphrase or a token: an
+SSH key that needs a passphrase has to be in `ssh-agent` (`ssh-add`), and an HTTPS remote needs
+a stored login (`gh auth login` or a credential helper). The next push or session start sends
+what waited. If your project keeps its record private, nothing
is shared; `cogit config git` shows which it is.
## Nothing is recorded
diff --git a/packages/cli/src/commands/doctor.ts b/packages/cli/src/commands/doctor.ts
index 07393a7..911ddd5 100644
--- a/packages/cli/src/commands/doctor.ts
+++ b/packages/cli/src/commands/doctor.ts
@@ -328,7 +328,7 @@ const CHECK_SPECS: CheckSpec[] = [
id: "record",
status: "warn",
message: `${sync.pending} session record${sync.pending === 1 ? "" : "s"} could not be sent: ${sync.sendError}`,
- fix: "check your access to the remote; the next session start tries again. An SSH key with a passphrase needs ssh-agent (`ssh-add`), since a background send cannot ask for it; `cogit record-sync send` sends from this terminal",
+ fix: "the send runs in the background, where nothing can ask for a passphrase or a token: add your SSH key to ssh-agent (`ssh-add`), or for HTTPS store your login (`gh auth login` or a credential helper). The next push or session start sends the queue",
};
if (sync.downloadError !== undefined && !sync.downloaded)
return {