Skip to content

Releases: hcipengm/cogneva

v0.5.10

Choose a tag to compare

@github-actions github-actions released this 19 Oct 15:19

Full Changelog: v0.5.9...v0.5.10

v0.5.9

Choose a tag to compare

@github-actions github-actions released this 19 Oct 12:48

Full Changelog: v0.5.8...v0.5.9

v0.5.8

Choose a tag to compare

@github-actions github-actions released this 24 Sep 06:10

Full Changelog: v0.5.7...v0.5.8

Assets

Static musl bootstrap binaries — the one-command installer downloads these, so a blank host needs no Rust toolchain:

Asset Bytes sha256
cogneva-bootstrap-v0.5.8-linux-x86_64 10270888 cad45425f592262bce72610d40ed03823234b29b17f42c88f29b5bb7a1e9a1e5
cogneva-bootstrap-v0.5.8-linux-aarch64 7187888 2087483f37141397b059f9ea078487483f3ebb3d682510ee13e02987cbbe2686
cogneva-image-v0.5.8-linux-x86_64.tar.gz 534397491 e3d3737fb1e19ba3240b454072854e8404911d3aff50d14744612f50d8f4ead7

cogneva-image-* is the prebuilt runtime image, imported straight into the K3s containerd; without it the installer falls back to a source build (1-3 h). Every artifact ships with a matching .sha256.

What changed in 0.5.8

  • One transport policy instead of three local guesses. Git operations pick SSH first on restricted networks and HTTPS otherwise; release assets are HTTPS-only, because an attachment is not a git object and SSH structurally cannot carry it.
  • The gateway bootstraps its own git identity. With a platform token it generates a keypair and registers it as a repo-scoped deploy key automatically; without one it generates the keypair and surfaces the public key for a human to install.
  • Meta-bootstrap defect sweep (found by reinstalling on a blank host): CN network classification now uses several signals instead of one probe; the helm path got a kubeconfig and object ownership metadata; the CN image override table is generated from values.yaml; a rollout that never becomes ready is reported as a failure instead of "deployment complete".
  • Stale literal env values are cleared before a manifest is applied. A workload whose env moved from a literal to valueFrom used to be permanently un-appliable, and it aborted the whole kubectl apply -f <dir> batch with it.

Where each file lives: the bootstrap binaries and their .sha256 files are attached here and mirrored byte-for-byte on the Gitee release under the same names. The image is a single archive here and 95 MB parts on Gitee.

v0.5.7

Choose a tag to compare

@github-actions github-actions released this 04 Sep 11:27

What is this

Cogneva is a multi-agent platform that runs, heals, and evolves itself inside a K3s / Kubernetes sandbox. A single command takes a blank Linux machine to a working system:

curl -fsSL https://raw.githubusercontent.com/hcipengm/cogneva/main/bootstrap.sh | sh

What's in this release

Easier to install

  • One command, fully hands-off. The bootstrapper probes CPU, memory, node count and network, then decides whether to set up lightweight K3s or production-grade standard Kubernetes (falling back to K3s automatically when resources are tight). On networks with restricted access it switches to regional mirrors automatically.
  • Ready in minutes, no on-machine build. Install first downloads a prebuilt, self-contained image bundle and imports it (minutes); it only falls back to compiling from source (1–3 hours) when the download is unavailable.
  • Three deployment shapes, one config. Single-node K3s, multi-node K3s and standard K8s are all auto-detected; internal secrets are generated randomly at install time — no more default weak passwords.

Faster and more reliable

  • Self-upgrades went from hours to seconds. After the platform writes and builds a new version, it ships a tiny incremental image through an in-cluster registry and every node pulls it in seconds — measured end-to-end under 5s (the old path recompiled on the node, taking 1–3 hours).
  • Every running version is traceable. The binary reports its version and exact source commit at any time; version swaps are cross-checked automatically, so you can never silently run a month-old build while thinking you're up to date.
  • Root-cause-aware self-healing. Failures are classified into six categories (network, code, resource, config, external dependency, unknown) and mapped to recovery strategies.
  • Secrets live in exactly one place. All outbound credentials (LLM keys, GitHub/Gitee tokens) are held only by the security gateway; the application pods themselves hold none, shrinking the blast radius.
  • Commands run in an isolated sandbox executor, separate from the main app.

Smarter to use

  • Watch agents work live in the browser. The Live panel streams real data — agent thinking, task progress and cluster topology — and you can dispatch tasks straight from the chat.
  • Set up your LLM with one wizard. A post-login wizard guides you through the credentials, auto-detects the API protocol, supports failover across multiple upstreams, and is not tied to any model vendor.
  • A smarter GitHub/Gitee bot. It reads the entire issue/PR thread before deciding whether to act, stops re-prompting on conversations that are still unanswered, and treats incoming pull requests as first-class inputs for self-evolution.
  • China-network friendly. Mirrored on both GitHub and Gitee so installs aren't bottlenecked.

Fast install (prebuilt image)

The one-command installer downloads the prebuilt image bundle and imports it into containerd (minutes), falling back to a source build (1–3h) only if the download fails.

GitHub hosts the full bundle cogneva-image-v0.5.7-linux-x86_64.tar.gz plus its .sha256. On Gitee the bundle is split into 95MB parts (.part-aa … .part-af) with the same .sha256; the installer downloads and joins the parts automatically and verifies the checksum of the joined file — no manual steps needed.