Game developer uses OpenClaw for automated feedback collection and code refactoring

A game developer has detailed their setup using OpenClaw as a background service (LaunchAgent) on a MacBook to manage two development projects. The system connects Claude (Anthropic's model) to Discord servers and Telegram for direct interaction and autonomous task execution, with all memory stored locally in Markdown files that are read on startup.

Heretical Project: Automated Player Feedback Collection

For the Steam game Heretical, the developer has configured an automated nightly workflow that runs at 11 PM:

• Pulls recent messages from key Discord channels (suggestions, discussion, feedback, bug-reports)
• Fetches recent Steam reviews via the Steam API
• Searches Reddit and the web for mentions
• Cross-references against known issues (camera rotation, onboarding, missing SFX, etc.)
• Writes a dated Markdown report to a local Obsidian vault
• Commits and pushes the report to a private GitHub repo
• Posts a summary to a Discord #monitoring channel

This provides a daily digest of player feedback without manual monitoring.

Duskland Project: Autonomous Code Development and Refactoring

For the TypeScript project Duskland, the developer uses a "vibecoded" approach where they define desired outcomes and let the system handle implementation. The workflow includes:

A specific prompt posted to Discord when the system restarts:

Summarize the request and split it into tasks.
You send the summary back to the chat immediately and a confirmation that you'll spin up claude code with claude opus 4.6 for each of the tasks.
You start claude code with opus 4.6 and execute one task after the other.
Every 5-10 minutes you report back here with the status update - how's it going, if claude code is running or it timed out (and restart it if it timed out).
Once it's done, you do a final report here with the results. Claude should build it locally to verify that the build isn't broken and so that I can check it in the browser.
Push the changes to the git repository.

Additionally, an autonomous refactor pass runs at 5:30 AM nightly:

• Checks for new commits since the last refactor (skips if nothing new)
• Runs Claude Opus to analyze the codebase and identify 1-3 small, focused refactor tasks
• Executes each task one at a time with Claude Code (also Opus), committing after each one
• Runs tsc and npm run build to verify nothing broke — reverts if it does
• Saves a summary, then at 9 AM posts a refactor report to Discord

Maintenance and Backup

The system includes automated maintenance:

• 4:00 AM - Bot updates itself: pulls latest OpenClaw, skills, and plugins, then restarts
• 4:30 AM - Backs up all config, memory files, workspace, and cron definitions to a private GitHub repo

Daily Interaction and Infrastructure

Day-to-day interaction happens through Discord chat, where the developer can ask about player feedback, draft posts, check recent commits, or review overnight activities. The system maintains persistent memory across sessions via local Markdown files and runs on existing hardware with no cloud subscription beyond API costs. The developer uses a premium Anthropic subscription with Claude Sonnet for chats and Claude Opus for code edits.