본문으로 건너뛰기

0.2.1

번역 준비 중

이 쪽은 아직 한국어로 옮기지 않았습니다. 아래는 영어 원문입니다.

A security fix for S3 storage, fixes found by installing on a bare Ubuntu 26.04 machine, and options that are now simply on.

Install​

curl -fsSL https://github.com/ElanvitalAI/elanous/releases/latest/download/install.sh | bash   # one line

npm had not been updated for 0.2.1; the one-line installer above is the way to install this release.

S3 storage: no default bucket​

Up to 0.2.0, S3 features (session backup, memory archive, metrics and others) fell back to a built-in bucket name when you had not set one. That bucket belongs to the project and allows public reads, so this was never the right default.

  • There is no default bucket any more. Without configuration nothing is uploaded — features keep working locally.
  • Two buckets, set in ~/.elanous/config.json (or the environment):
{ "storage": { "s3": { "bucket": "my-private-bucket", "publicBucket": "my-public-bucket" } } }
keyenvironmentused for
storage.s3.bucketAWS_S3_BUCKETeverything private: sessions, memory archive, metrics
storage.s3.publicBucketAWS_S3_PUBLIC_BUCKETonly features that hand out public links: publishing, morning report, debug bundle
  • Keep bucket private (block public access). Only publicBucket should be publicly readable.

Fixes from a bare Ubuntu 26.04 install​

  • /harness ask in the TUI now actually starts the run in your project. It printed «run launched» but the background run could not find elanous's own entry script outside the elanous source tree and exited silently.
  • The TUI harness on a repository without a git remote now finishes on a local worktree branch instead of failing at the pull-request step (it tells you so in one line). Pass the completion flags yourself on the CLI if you really want a PR.
  • Your repository stays clean: the .elanous/ folder elanous creates inside a project (debug logs, goal documents) is added to that repository's local .git/info/exclude — your .gitignore is not touched.
  • No more «no crontab for …» in the middle of the TUI on machines without a crontab.
  • Queued input shows how to take it back: ⏳ … · Ctrl+↑ 되꺼내기. Inside tmux, enable extended keys first: tmux set -s extended-keys always.
  • Setup wizard: the provider line no longer names old models, and «recommended» is shown once.

Options that are now always on​

These had been on in practice for months; the switches are gone and elanous doctor lists them as keys you can delete:

  • instance.treeDerivedTest — a non-leader checkout runs in its own test state; a fresh install with no leader is unaffected.
  • tools.selfImplement.selfResolveClarifications — elanous self author answers its own clarification questions from repository evidence, as harness ask/say already did.
  • ACP_PERSIST_MODE, ACP_BG_SWEEP_MODE, PWA_VOICE environment switches and prEvidenceArtifactEnforce — removed; the enabled behaviour (or observation) stays.

Also​

  • elanous graph run <file> [--dry-run] · elanous graph status <id> — walk an operations graph whose nodes run registered recipes.

Release page