KitewellRelease status
← All chores

Every Monday

Every Monday I update our dependencies, run the tests, and lose the morning fixing whatever broke.

How it goes now

git switch -c deps.Bump everything.Run the tests.Red.Read three changelogs.Fix.Run the tests.Push. Open the PR.

Every Monday morning.

Tell Kitewell once

You
Every weekday at 2:00, have my Codex agent update the dependencies in my repo on a branch named deps/nightly, run the tests, and commit. Wait for my approval, then push the branch and open a PR.

That's the whole setup. Kitewell lays out every step for you to check, and nothing is saved until you apply it.

Then it runs on its own

Dependency updateRunning on this computer

  1. Update dependenciesCodex branches, updates, runs the tests, fixes what broke, and commits. Its notes are saved.Done
  2. Wait for your OKNothing is pushed until you approve, in Kitewell or from your phone through Claude.Waits for you
  3. Push and open the PRgit push --force-with-lease, then gh pr create.Done

What you get instead

Update dependencies

  • Updated 14 packages, 2 of them major versions.
  • Fixed a renamed option in the date library.
  • All 312 tests pass.

Push the deps/nightly branch and open a pull request?

Sample data

Good to know

  • By default the agent may only read its working folder and asks before anything risky. It works with the sign-in it already has; Kitewell supplies no AI credits.
  • Approving from your phone needs Claude connected to Kitewell, which uses a Dagu Cloud sign-in.
  • Your computer needs to be on and awake when it runs. A run missed while it slept starts when it wakes, within 24 hours by default.

What it needs

  • A command-line agent such as Codex or Claude Code, installed and signed in
  • A Git repository and the gh command

More chores