@ibuprod@iBUKAR3L@sama if that’s the case, i guess my question is, what’s the advantage of using openclaw other than ease of use to message it via tg/wa? CC is already the orchestration agent and can write its own prompts based on the context of your codebase, tho multimodel vs codex/cc separately…
@ibuprod@iBUKAR3L@sama ya for sure. if you have checked out the GSD skill on CC, def check it out. the built up memory is rly just a ton of .md files anyways for openclaw, also opus is 1M token context now too. my general opinion is no need for openclaw for the actual coding but open to other opinions
@ibuprod@iBUKAR3L@sama yea hard to say with the limited knowledge i have of your workflow, but presumably, the agent is just taking your QA inputs and then scaffolding plan -> solution -> sprint > test. memory and session constraints are “easier” to get around now since you can have CC write memory