docs(kiloclaw): add infrastructure specs and fix stale RAM value#1098
Open
kilo-code-bot[bot] wants to merge 1 commit intomainfrom
Open
docs(kiloclaw): add infrastructure specs and fix stale RAM value#1098kilo-code-bot[bot] wants to merge 1 commit intomainfrom
kilo-code-bot[bot] wants to merge 1 commit intomainfrom
Conversation
…GENTS.md - Add kiloclaw/docs/infrastructure-specs.md documenting all hosting and instance specs (Fly.io machine sizes, volumes, regions, networking, CI/CD pipeline, Cloudflare control plane, etc.) - Fix AGENTS.md default machine spec: 4GB -> 3 GB (3072 MB) to match the actual DEFAULT_MACHINE_GUEST in src/config.ts
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
| | --------------------- | ------------------------------------ | -------------- | | ||
| | App name pattern | `acct-{hash}` | `dev-{hash}` | | ||
| | Shared image registry | `kiloclaw-machines` | `kiloclaw-dev` | | ||
| | Legacy fallback app | `kiloclaw-machines` (`FLY_APP_NAME`) | — | |
Contributor
Author
There was a problem hiding this comment.
SUGGESTION: Development fallback app is documented as absent
The worker still uses FLY_APP_NAME as the legacy fallback in development, and kiloclaw/.dev.vars.example sets that value to kiloclaw-dev. Leaving the dev column blank makes this matrix inaccurate for local/dev setups.
Suggested change
| | Legacy fallback app | `kiloclaw-machines` (`FLY_APP_NAME`) | — | | |
| | Legacy fallback app | `kiloclaw-machines` (`FLY_APP_NAME`) | `kiloclaw-dev` (`FLY_APP_NAME`) | |
Contributor
Author
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)SUGGESTION
Fix these issues in Kilo Cloud Other Observations (not in diff)N/A Files Reviewed (2 files)
Reviewed by gpt-5.4-20260305 · 833,750 tokens |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
kiloclaw/docs/infrastructure-specs.mddocumenting all hosting and instance specifications for KiloClaw, derived from the actual codebase configuration files with source-of-truth references for each value.kiloclaw/AGENTS.md: the default machine spec stated "4GB RAM" but the actual code insrc/config.tsdefinesmemory_mb: 3072(3 GB).Verification
src/config.ts:31-35(DEFAULT_MACHINE_GUEST.memory_mb = 3072)Visual Changes
N/A
Reviewer Notes
The infrastructure specs doc covers: Fly.io machine defaults (shared-cpu-2x, 3 GB RAM), configurable machine size range (1-8 vCPUs, 256 MB-16 GB RAM, shared/performance CPU), volume specs (10 GB NVMe), regions (dfw/ewr/iad/lax/sjc/eu), per-user app isolation, networking config, health checks, CI/CD pipeline, and the Cloudflare Workers control plane. No Terraform/Kubernetes/IaC manifests exist — all Fly resources are managed imperatively via the Machines REST API.