Alexander Wu

@voidking

I know the problem, because config.yaml has higher priority, so the stub in config.yaml blocks the env variable. I will fix this in the next update

https://github.com/geekan/MetaGPT/commit/da11d383e60bb4d1562ed08b9db2ff9ea5721328 pushed. check it again.

@qa6300525 Some fields can actually be ignored, because the post-role has no dependence on them, even if the parsing error does not affect the effect

https://github.com/geekan/MetaGPT/pull/41 almost fix this issue. pull & retry.

Pull again and retry. I've removed langchain.

This problem stems from the fact that gpt-3.5-turbo instruction follow is not stable enough (the success rate is about 30% visually, but it changes with the demand), gpt-4 will be...

https://github.com/geekan/MetaGPT/pull/41 and https://github.com/geekan/MetaGPT/pull/43 almost fix this issue. pull & retry.

This is a problem caused by the instability of the langchain code base. I will remove references to langchain as soon as possible.

removed in https://github.com/geekan/MetaGPT/commit/bd9d6e94674f7bef9553835c7bfa3b9ffd347f25. check it again.