Skip to content

v1.3.68

Choose a tag to compare

@topcheer topcheer released this 08 Jun 16:35
· 244 commits to main since this release

ggcode v1.3.68

Highlights

  • Safer tool orchestration guidance: Clarifies one-shot sub-agent behavior, tracked swarm tasks, teammate result collection, and when to use send_message versus swarm_task_create.
  • Persistent cron jobs: Recurring cron jobs are now persisted per workspace and restored on startup, while one-shot reminders remain in-memory only.
  • Desktop model and provider polish: Improves Wails desktop provider/model selection, reasoning-effort controls, status handling, layout behavior, and toast notifications.
  • Safer configuration tooling: Strengthens config tool guidance around provider-affecting changes and avoids echoing secrets in tool results.

Fixes and improvements

  • Added workspace-bound cron persistence and clarified cron tool persistence semantics.
  • Hardened command-job polling, command output handling, grep/search behavior, web fetch/search descriptions, git tool descriptions, worktree guidance, and plan-mode tool messaging.
  • Improved swarm/sub-agent/tool descriptions and tests so agents avoid duplicate task claiming, repeated completion, and unreliable sub-agent follow-up messages.
  • Added safer config tool wording for vendor/endpoint/model/API key changes, including probe-before-commit behavior and secret redaction in tool output.
  • Updated desktop Wails settings/provider flows, session/status reset behavior, sidebar/top drag bar UI behavior, and generated Wails bindings.
  • Added Review 55 documentation summarizing current application review findings and priority follow-up areas.
  • Expanded tests across provider, config, cron, command jobs, grep, web tools, task tools, swarm/team tools, TUI paste/layout flows, and desktop-adjacent behavior.

Upgrade notes

  • Only recurring cron jobs are persisted across restarts. One-shot reminders created with recurring=false are still in-memory and will be lost if the process exits before they fire.
  • If changing provider configuration through the config tool, inspect current settings and available models first; failed provider probes leave the current working configuration unchanged.

Compare