Phuriwaj

Freewrite

A focused day on AI tooling and project architecture. Wired up GitHub Actions to auto-implement issues via Claude Code using the Z.ai proxy, which makes the “write issue → get PR” loop fully automated with no manual coding step. Also clarified a persistent confusion around why Claude Code Remote Control doesn’t work with local LiteLLM setups — it’s an identity/session layer problem, not a model access problem. Capped the day by stress-testing the Django/Next.js project’s build order and confirming vertical slices are the right strategy.

Big Things Today

  • GitHub Actions autocode workflow set up — write issue, add label, PR appears
  • Confirmed vertical slice approach is correct for solo Django/Next.js project — no reordering of Jira plan needed

Conversations

AI Tooling

GitHub project automation with Claude

Adapted a GitHub Actions workflow to auto-implement issues using anthropics/claude-code-action@v1 with Z.ai as the proxy backend. The workflow triggers on the autocode label, runs Claude Code against the issue body, and opens a PR when done. Labels shift: autocodein-progressin-review. Z.ai uses glm-4.5-air for haiku calls and glm-5.1 for sonnet/opus, so cost is naturally optimised. → See github-actions-guide

CC-Remote Control

Clarified why API keys are inference-only and cannot activate Remote Control or Channels. Those features need OAuth login to claude.ai for session registration, identity verification, and push notifications. Local LiteLLM/DeepSeek proxy setups are fundamentally incompatible with Remote Control — the inference path must go through Anthropic’s actual API. → See claude-code-remote-control

Project Development

Django vs Next.js frontend choice

Debated all-backend-first vs all-frontend-first vs vertical slices for the ongoing Django + Next.js SaaS. Verdict: vertical slices (model → endpoint → frontend per feature) are correct for a solo developer on a 21-week plan. The existing Jira structure already uses this approach — no change needed. Phase 0–1 hardens the core data model before any feature work begins, which neutralises the main argument for all-backend-first. → See vertical-slice-solo-dev | vuexy-nextjs-frontend

Open Tasks Surfaced

  • Create GitHub labels: autocode, in-progress, in-review (gh label create)
  • Add ANTHROPIC_AUTH_TOKEN secret to GitHub repo for autocode workflow
  • Run Phase 1 Vuexy audit in Claude Code (paste the 12 claude-docs/ prompt)
  • Paste Lead agent prompt to kick off User Management Phase 4 (T068–T088)

Insights Worth Developing