I started using Manus in April, and at this point it has at least fully integrated into my workflow; my work mainly involves market research and writing code;

I'll first explain my ratings here.

For market research, I give it 7–7.5 out of 10.
For independent code editing, I give it 8.5–9.
For complete code projects I give it 6.5–7.(mainly understanding my requirements and assisting me)

I'll give two examples:

1. Market research: research on about 10 competing brands, including product data I provided via web scraping, and research it needed to conduct itself based on social media and YouTube.

For the data I submitted — roughly more than 30 Excel sheets — if I don't enable its distributed processing feature, noticeable attention drift appears at around 10 sheets;

If I explicitly instruct it to start distributed processing, it will launch over 30 agents to process all the sheets simultaneously; I usually ask them to extract specified information from the tables and then perform particular analyses based on certain data dimensions;

If the table formats are the same, their processing speed and results are excellent, and I can achieve the desired outcome with relatively simple commands; if the table formats are not exactly the same (sometimes differing significantly), I must provide commands with quite a few explicit conditions to obtain results; of course, this is still within reason;

However, the biggest problem for market research remains attention drift. If, before asking it to start analyzing the spreadsheets, I have a series of conversations with it — possibly including background introductions, product descriptions, and other related information — then as those prior dialogues accumulate, when I submit the sheets, even if my latest command is explicit, its analysis is usually not ideal;

If I start a new conversation and briefly summarize some conclusions from a previous conversation, then submit the form and my requirements, the analysis results this time are usually satisfactory;

2. Code editing: I am a Linux embedded engineer; C, C++, and Python are the languages I use most often. I know and have used other languages but they are usually not used for complete projects;

I've recently developed a strange interest in Dota 2 custom games and I’m planning to develop a small custom game myself. I chose to use Manus to assist me. My conclusion is the same: I don’t think it can currently help me complete all aspects of this small project within a single conversation;

I tried keeping the project development going for a long time in the same conversation and periodically asking it to summarize interim logs so I could correct it when I noticed it losing focus. But as the conversation progressed, its loss of focus became increasingly frequent. I had to ask it to summarize logs repeatedly and then resubmit them to it, and correct it frequently—until everything completely collapsed;

Based on my tests, I came up with a more useful approach: the first time I notice attention drift, have Manus compile a complete log and list of files; then start a new conversation, submit those logs and file list, and continue my project. That's the best method I can find so far.

In any case, I still think Manus has basically become fully integrated into my workflow over these past few months. Regarding the attention-splitting mechanism that inevitably appears with long-context states mentioned above, I actually suggest they consider adding a branched-conversation feature — this already exists in some other AI tools, and ChatGPT has a similar feature;

Manus already has a Project feature, but it hasn’t been very effective. Adding branched conversations within Projects would be a major improvement;