View on Asset Store (opens in new tab)
Package details
- Latest version
- 1.0.2
- Last updated
- First released
- Unity version
- 6000.4.1 or later
- Package size
- 250 KB
- Files
- 26
- Favorites
- 3
- Views in the past week
- 4
Price tracking
- Last checked
- Tracked since
- Lowest recorded
- $20.99 on
Keywords
ClosUrLoop
Unity 6 task-closer. Finish what you start with CeaseL, a local, privacy-first coach. Kill task rot and stay in flow with bounded work cycles and strict focus caps. Mechanics with Meaning.
Affiliate link · Purchases support this site
Price history
Last 6 months
USDAsset preview
1 / 3
ClosUrLoop screenshot 1
About this asset
ClosUrLoop: Bounded Workflow for Unity 6
Mechanics with Meaning. Systems with Soul.™
What this package is
ClosUrLoop is an Editor-only workflow architecture designed to solve the "90% finished" problem. It provides a dedicated workspace to define small, concrete tasks and move them through a deterministic lifecycle: Planned → In Progress → Done.
To fight backlog sprawl, ClosUrLoop enforces a Strict Focus Cap. It prevents you from juggling an endless list, forcing you to either Lock a task as truly finished or Abandon it with a tagged reason.
The CeaseL Engine (Optional)
CeaseL is your rule-based developmental coach. Built on local logic—not the cloud—CeaseL monitors your Editor context (compile patterns, play-testing frequency, and console noise) to provide authored feedback based on your actual work habits.
- 100% Private: No telemetry, no generative AI, and no "phoning home."
- Deterministic: Responses are triggered by scripted behaviors, not random seeds.
Project Fit & Customization
- Genre Agnostic: Suitable for any Unity 6 project (Indie, AA, or Enterprise) where execution hygiene is a priority.
- Customizable Content: While the core workflow rules are fixed by design, you can fully tune CeaseL’s tone, cadence, and message bank via the JSON files located in Resources/CeaseL/.
- Zero Runtime Cost: As an Editor-only tool, it adds zero overhead to your final game builds.
The Kiklios Philosophy: This tool is not a magic fix for procrastination. It is a mirror for your workflow. This tool only works if you are willing to let it.
From the publisher's Asset Store listing.
Technical details
Key features
- Unity 6 Editor companion — Runs in the Editor only (open via ClosUrLoop → ClosUrLoop). Does not add a runtime gameplay dependency for your shipped build.
- Honest task lifecycle — Tasks move through Planned, In Progress, Done, Abandoned (with tagged reasons), and Locked for deliberate closure.
- Focus cap (strict) — Limits how much can stay active at once so work stays bounded instead of growing an endless “open loops” list.
- CeaseL (optional coach) — Rule-based, local coaching using JSON-driven behaviors and messages; Silent / Balanced / Coach-style voice profiles.
- Editor-aware signals — Reacts to patterns like compile churn, play mode usage, console noise, task churn, idle work, and window open/close (with domain-reload-safe handling where appropriate).
- Privacy-first — No accounts, no cloud, no telemetry; tasks and coach memory save as local JSON under Unity’s persistent data path.
- Packaged documentation — PDF + Markdown user manual alongside LICENSE (EULA) in the asset folder: setup, requirements, API sketch, full CeaseL behavior catalog reference, troubleshooting.
- Self-contained import — Drop Assets/ClosUrLoop into a project (or use your .unitypackage); includes Runtime, Editor, Resources (catalogs + message bank), asmdefs.
- Tunable authored content — Edit CeaseL JSON (behavior catalog, policy, English messages) to adjust coaching lines, pacing, and behavior mix without changing Unity C# (within the shipped rule framework).
Compatibility
| Unity version | Built-in | URP | HDRP | Custom |
|---|---|---|---|---|
| 6000.4.1f1 | Compatible | Compatible | Compatible | Compatible |
ClosUrLoop runs in all pipelines (Built-in, URP, HDRP). The core logic, tasks, and CeaseL are render-agnostic.
Note: The included demo scene uses a URP template. In non-URP projects, Unity may report missing scripts on the demo's Camera or Light. This does not affect the tool. Simply Remove Component on missing scripts or replace with your pipeline's native camera/light.
As listed on the Asset Store.