Skip to content

LoopSkill 4.1.0

Choose a tag to compare

View all tags
@amanayayatu-tech amanayayatu-tech released this 31 Jul 07:35
· 24 commits to main since this release
v4.1.0
81d4f35
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

LoopSkill 4.1.0 release notes

Status: LoopSkill 4.1.0 is the current public v4 release.

LoopSkill 4.1 helps turn work that can outlive one chat into a bounded process:
state the goal, inspect the scope, confirm once, and check the result against
machine evidence. The visible flow remains
INTAKE → PREPARE → CONFIRM → START; it does not silently start a Host task.

User-visible changes

  • Start from one sentence, pasted PRD text, or one explicitly authorized UTF-8
    text/Markdown file. Ordinary users do not write JSON.
  • Conversational intake retains confirmed answers for the current session and
    asks at most three questions that truly block preparation.
  • PREPARE shows the confirmed boundary, plan summary, and capacity report.
    START THIS LOOP remains an exact, independent user confirmation.
  • One confirmed plan may contain 1–32 Goals. Only the current Goal is activated;
    subsequent Goals reuse the existing atomic AdvanceGoal transition.

Capacity and compatibility

  • Canonical PlanDocument: at most 128 KiB.
  • Explicit UTF-8 text/Markdown source: at most 256 KiB.
  • CreateLoop release target: 8 KiB / 64 members; hard limit remains 16 KiB /
    128 members.
  • Materialized Host prompt target: 24 KiB; hard limit remains 32 KiB. Overflow
    is rejected before Host execution and is never truncated.
  • New Loops use CONTENT_ADDRESSED_V1. Existing EAGER_V4_0 stores support
    status, export, and original-reducer continuation only. There is no migration,
    rewrite, or dual write.
  • LoopSkill 4 is a v4-only hard break. It does not open, import, repair, or
    automatically migrate v3 data. Users who need the historical v3 line can use
    LoopSkill v3.3.8.

Safety boundary

LoopSkill still uses one canonical Store writer, at-most-one automatic Attempt
per activation, bounded foreground Codex execution, and honest UNKNOWN /
UNVERIFIABLE outcomes. It does not register MCP, edit Codex configuration,
require an App restart, start a daemon, restore v3 runtime, promise cross-system
exactly-once, support multiple Hosts, or claim patch-success or proven
long-horizon superiority.

Release validation used deterministic matrices plus a fresh 2-Goal and, only
after it passed, a fresh 8-Goal real Host canary on the same exact clean
candidate. Those 10 invocations are product validation, not research evidence.

Assets 2
Loading