Skip to content

fix(deploy): size the edge controller Container at standard-2 - #20

Merged
RedStar071 merged 1 commit into
mainfrom
fix/edge-container-size
Oct 19, 2026
Merged

RedStar071 merged 1 commit into
mainfrom
fix/edge-container-size

Conversation

@RedStar071

Copy link
Copy Markdown
Member

🔗 Linked issue

Related to the Cloudflare budget alert on the Containers spend. This repository has issues disabled.

❓ Type of change

  • 📖 Documentation
  • 🐞 Bug fix
  • 👌 Enhancement
  • ✨ New feature
  • 🧹 Chore
  • ⚠️ Breaking change

📚 Description

The edge controller Container never sleeps: onActivityExpired renews its timeout and the cron restarts it. Cloudflare bills Container memory and disk for every hour it runs, so the instance size sets the monthly cost. At standard-4 (12 GiB) the memory alone is roughly $77 a month on the published rates.

This sets instance_type to standard-2 (1 vCPU, 6 GiB, 12 GB disk), which roughly halves that. The host capacity check already derives the Agent count from memory (4 GiB per Agent, 2 GiB reserved), so one Agent runs at a time instead of two. max_instances stays at 1, now with a comment that raising it multiplies the always-on cost. The README table and a comment in cloudflare-runtime.ts follow the new size.

Operator note: the 12 GB disk holds every repository the App clones at start. If it fills, move to standard-3 (2 vCPU, 8 GiB, 16 GB).

🤖 AI disclosure: Wolfstar Agent Kit modified this description. AI open source policy.

The controller never sleeps, so Cloudflare bills its memory and disk all month. standard-4 (12 GiB) cost about twice standard-2 (6 GiB) for a second concurrent Agent. The host capacity check already derives the Agent count from memory, so one Agent runs at a time.
@coldtea-pr-lens

coldtea-pr-lens Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Architecture

Architecture diagram for wolfstar-project/wolfstar-agent-kit at c68f886

Open the canvas


Data flow

No data-flow sequence changed in this PR.


Review

✨ Nothing flagged · reviewed c68f886


Tip

Open a diagram on the canvas, then press W or click play to walk through the change one step at a time

🪧 More tips
  • Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
  • Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists
  • Click the link under each diagram to open it on a canvas you can zoom, pan and step through
  • The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change
  • The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time
  • Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture and data flow row. Drawing still runs as before
  • Set github.draw: on-demand in .github/pr-lens.yml and PR Lens stops drawing pull requests on its own. Comment @pr-lens draw on a pull request when you want that one drawn
  • Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works
  • After a push, tick Redraw to draw the latest commit
  • Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion

Thanks for using PR Lens! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out on X, Bluesky, Mastodon, Reddit or LinkedIn

@RedStar071
RedStar071 merged commit 5ba31a3 into main Oct 19, 2026
9 checks passed
@RedStar071
RedStar071 deleted the fix/edge-container-size branch October 19, 2026 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant