openclacky 0.7.8 → 0.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9b2a72212b8b9e8072acb09a055df1afdd8225ee81de41f11dce460a68ff1781
-  data.tar.gz: e8048bb38dc4a8ae8c85937165e10a855f8642d6759c8a2a94aa336b084e4188
+  metadata.gz: 847578e565b36373d9941ed108df7b68a78a3b485681f22f606637f90f3f6a49
+  data.tar.gz: 638855b903c61169486422f5d791a3eb7a7b4751cdee5a3b757abaf4fdd32ff2
 SHA512:
-  metadata.gz: '095710e060b7c29882eb128be1a4008281435c13af07e7da01ec9ad1af27c30e252eb19e77f557882628409058d504f29024ea0dbb396ed20d326b26cfe1925c'
-  data.tar.gz: 2875ac5911322341be5fe396ad44a98e4cbcea51c95ed7d832e3978d5790542ca94ae0f065f6170484d9900be2f1ca190f6db0d25c14a33366f924f9d13a147d
+  metadata.gz: 981a682c39c603d101c7755e3bdeecf053519e2eb041120311a4877c2aac9370bbc24cf57ead31595636592eb75513c6844faf9418cf378bb1c767e506b560e0
+  data.tar.gz: f7cbdcadf728ddc1825d9f11827f3dc8843981005a59cb5851391580d3f91e25b7f2f32730b928702ea3ad638c54e7c2f2134d0d16d47173dd37816d51e290e5

data/.clacky/skills/gem-release/SKILL.md

@@ -190,10 +190,38 @@ To use this skill, simply say:
    - Commit CHANGELOG.md changes
    - Push to remote repository
 
-### 7. Final Verification
-- Confirm the gem appears on RubyGems.org
-- Check that version information is correct
-- Verify installation works for end users
+### 7. Final Summary
+
+Present a clear, user-facing release summary after all steps complete:
+
+**Format:**
+```
+🎉 v{version} released successfully!
+
+📦 What's new for users:
+
+**New Features**
+- [translate each "Added" item into plain user-facing language]
+
+**Improvements**
+- [translate each "Improved" item into plain user-facing language]
+
+**Bug Fixes**
+- [translate each "Fixed" item into plain user-facing language]
+
+🔗 Links:
+- RubyGems: https://rubygems.org/gems/openclacky/versions/{version}
+- GitHub Release: https://github.com/clacky-ai/open-clacky/releases/tag/v{version}
+
+Install/upgrade: gem install openclacky
+```
+
+**Rules for writing the summary:**
+- Write from the user's perspective — what can they now do, or what problem is now fixed
+- Avoid technical jargon (no "cursor-paginated", "frontmatter", "REST API" — explain what it means instead)
+- Skip "More" / chore items unless they directly affect users
+- Keep each bullet to one sentence, action-oriented
+- Example translation: `fix: expand ~ in file system tools path arguments` → "File paths starting with `~` (home directory) now work correctly in all file tools"
 
 ## Commands Used
 
@@ -248,6 +276,7 @@ gh release create vX.Y.Z \
 - CHANGELOG.md updated with release notes
 - GitHub Release created and visible at https://github.com/clacky-ai/open-clacky/releases
 - No build or deployment errors
+- User-facing release summary presented at the end
 
 ## Error Handling
 

data/CHANGELOG.md

@@ -7,6 +7,44 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.8.0] - 2026-03-06
+
+### Added
+- White-label brand licensing system: customize the web UI with your own name, logo, colors, and skills via `brand_config.yml`
+- Brand skills tab in the web UI with private badge, shown only when brand skills are configured
+- Slash command prompt rule: skill invocations (e.g. `/skill-name`) are now expanded inside the agent at run time, enabling mid-session skill triggering
+
+### Improved
+- Server-side brand name rendering eliminates the first-paint brand name flash in the web UI
+- Collapsible tool call blocks in the web UI — long tool outputs are now grouped and collapsed by default
+- `safe_shell` now catches `ArgumentError` in addition to `BadQuotedString` for more robust command parsing
+- Eliminated `Dir.chdir` global state in session handling, fixing race conditions in concurrent sessions
+
+### Fixed
+- Skill slash commands are now expanded inside `agent.run` so that `/onboard` and similar commands work correctly when triggered mid-session
+- Observer state machine handles `awaiting` state transitions properly
+
+### More
+- Disabled ClaudeCode `ANTHROPIC_API_KEY` environment variable fallback in `AgentConfig` for cleaner env isolation
+- Updated gemspec, lockfile, and install script
+- Added web asset syntax specs and brand config specs
+
+## [0.7.9] - 2026-03-07
+
+### Added
+- Cursor-paginated message history in web UI for large session navigation
+- `confirm_all` permission mode for WebUI human sessions
+- Re-run onboard entry in settings panel
+
+### Fixed
+- Expand `~` in file system tools path arguments (file_reader, glob, grep, write, edit)
+- Sort sessions newest-first with scheduled sessions at bottom
+- Tasks and skills sidebar items now static — no longer disappear on scroll
+- Delete task now also removes associated schedules
+
+### More
+- Add frontmatter (`name`, `description`, `disable-model-invocation`, `user-invocable`) to onboard skill
+
 ## [0.7.8] - 2026-03-06
 
 ### Added

data/docs/agent-first-ui-design.md

@@ -0,0 +1,77 @@
+# Agent-First UI Design Philosophy
+
+> Guiding principle for all OpenClacky UI and feature design.
+
+---
+
+## Core Principle
+
+**Conversation first, interactive cards when needed.**
+
+Users interact with the Agent through natural language to accomplish everything. When conversation is inconvenient for structured input (e.g. dropdowns, multi-select, precise time picking), the Agent triggers an **interactive card** via the `request_user_feedback` tool — rendered by the frontend as a structured UI component. Cards are a complement to conversation, not a replacement.
+
+---
+
+## Two Interaction Modes
+
+### 1. Conversation (default)
+User expresses intent in natural language, Agent understands and executes.
+
+```
+User:  Send me a daily standup summary every morning at 9
+Agent: Done! Task created, runs Mon–Fri at 09:00 ✅
+```
+
+### 2. Interactive Cards (when conversation falls short)
+When the Agent needs structured input that's hard to express in free text, it calls `request_user_feedback`. The frontend renders this as an interactive card (dropdowns, radio buttons, time pickers, etc.).
+
+```
+Agent calls request_user_feedback → frontend renders a card:
+
+┌─────────────────────────────┐
+│ 📋 Confirm task settings     │
+│ Frequency: [Daily      ▼]   │
+│ Time:      [09:00      ]    │
+│            [✅ Confirm] [Cancel] │
+└─────────────────────────────┘
+
+User fills card → structured data sent back to Agent → execution continues
+```
+
+---
+
+## When to Use Cards
+
+| Situation | Reason |
+|-----------|--------|
+| Choosing from a list of options | Easier than enumerating in chat |
+| Date / time selection | Precise value, error-prone in free text |
+| Sensitive input like API keys | Should not appear in conversation history |
+| Collecting multiple fields at once | One card beats several back-and-forth questions |
+
+Everything else: use conversation.
+
+---
+
+## What Should NOT Exist
+
+- ❌ Persistent configuration form pages
+- ❌ Fields that require users to understand technical details (cron expressions, agent IDs, etc.)
+- ❌ More than 3 action buttons per list row
+- ❌ Standalone "Create" form modals
+
+---
+
+## Role of UI Pages
+
+UI pages are for **displaying state**, not for configuring things:
+
+- ✅ Show task lists, run history, current status
+- ✅ Minimal action set per row: ▶ Run / ✎ Edit (opens conversation) / ✕ Delete
+- ❌ No inline create/edit forms inside list pages
+
+Clicking "Edit" opens an Agent conversation with context pre-filled. The Agent drives the modification flow from there.
+
+---
+
+*Applies to all OpenClacky Web UI and feature design.*