Autonomous AI sales agent powered by Claude Code or Codex. Finds prospects, writes cold emails, sends campaigns, handles replies, books meetings. No API keys needed — runs on your Claude or Codex subscriptions.
Merge remote-tracking branch 'origin/main' into feat/warmup-ramp
Ethan02272e4e262f
diff --cc CHANGELOG.mdindex 1729cb1,88d9acc..4026030--- a/CHANGELOG.md+++ b/CHANGELOG.md@@@ -33,13 -21,18 +33,25 @@@ minor versions can still change behavio### Fixed+- A follow-up no longer goes out before, or right after, the email it+ follows. Each step now waits until the previous one has actually been sent+ and its gap (at least a day) has passed. Before, approving a batch of drafts+ late, or resuming after a pause or a compliance hold, could send a whole+ sequence within minutes, or step 2 before step 1. A follow-up whose earlier+ email was rejected or failed is cancelled instead of arriving as a first+ email.+ - **Windows:** text files (harvey.yaml, .env, prompts, skills, trained+ output, tokens, exports) are read and written as UTF-8 instead of the+ locale code page, so `harvey train` no longer crashes on characters like+ "★" and prompts aren't garbled; command output is UTF-8 too, so the+ dashboard's log of `harvey run` can't crash on "⚠". An npm install's+ `claude.cmd` shim is resolved to the native `claude.exe` it wraps and is+ never run through cmd.exe, which would re-parse Harvey's isolation flags;+ if the executable is missing, Harvey says how to fix it. Files an older+ Harvey saved in the Windows code page (trained skills, harvey.yaml) still+ load, with a warning to re-save them as UTF-8. `harvey export` CSVs are now+ UTF-8 on Windows too, which sequencers expect (Excel needs Data > From+ Text/CSV to show accents). Based on #18 by Tariz Shahid.- Replies are read without the email they quote. The model, the stored threadand the answer get the reply without the quoted email, and any line thatrepeats what Harvey sent that person is set aside, so Harvey's own words