Skip to main content
As of April 16, 2026, existing Charlie customers are already running on v2. Migration is mostly about how you structure guidance, not flipping a product switch.

​
Mindset shift in v2

v1 often felt like short call/response loops. v2 is built for more autonomous, long-running jobs that can plan, delegate, and complete work with less back-and-forth.

​
Migration steps

  1. Move instruction guidance into AGENTS.md.
    • If you used .charlie/instructions/*.md, consolidate the durable rules into AGENTS.md.
    • Root-level AGENTS.md is the best default.
  2. Move v1 playbooks into skills.
    • Convert each playbook into .agents/skills/<skill-name>/SKILL.md.
    • Invoke a skill with $<skill-name> in your request.
  3. Move proactive behavior to Daemons.
    • Define recurring automation in .agents/daemons/<daemon-id>/DAEMON.md.
    • Keep daemon scopes narrow first, then widen once behavior is stable.