Optimal Usage Strategies

Understanding the Credit-Based System

The Manus system has evolved from a model of single, long-running daily tasks constrained by a context cap to a new, more flexible paradigm: unlimited task sessions where progression is facilitated by credits. Understanding this transition is key to maximizing productivity and minimizing unnecessary credit expenditure.

Context Management

The primary challenge with the "single long session" approach within the current credit system revolves around context management. As any given task session progresses, accumulating instructions, files, generated content, and conversational history, its operational context inevitably expands.

• The longer and larger the context within a single session becomes, the more credits that session tends to consume
• This correlation is a major driver of high credit usage, especially if you're attempting to push a single task until it hits a functional context limit
• As the context window grows excessively large, any AI model, including Manus, tends to become less focused, potentially slower, and generally less productive
• Manus operates at its peak when dealing with a lower, more relevant, and focused context

The New Optimal Method

The superior method within the current Manus framework lies in fully embracing the capability to initiate as many distinct task sessions as required:

1. Embrace modularity: Conceptualize your projects as collections of modules or compartmentalized assets
2. Focus on completing one specific, manageable part within the scope of a single, dedicated task session
3. Pivot when necessary: Once you've achieved meaningful progress or reached a natural stopping point:
   • Stop that session
   • Start a completely fresh task
   • Strategically bring the essential progress over

This technique of "pivoting" – concluding one session and immediately beginning another with carried-over results – allows you to:

• Reset the context with each new task
• Continuously leverage the high performance of a fresh session
• Avoid the pitfalls of context bloat
• Achieve substantial credit savings compared to letting context accumulate indefinitely

Progress Transfer Methods

Manus offers several robust methods to ensure continuity without carrying over unnecessary context bloat:

1. Direct File Attachment: Manually select and attach only the relevant output files (code, text documents, images, etc.) to the new task's starting prompt
2. Public Share Link: Copy the public share link generated by the completed session and provide this link to Manus within the prompt of the new session
3. Sandbox Link: Provide the sandbox link from the previous session, allowing the new session to access the staging environment (use with caution)
4. GitHub Integration: For code-heavy or complex projects, use GitHub as a persistent repository:
   • Commit your progress from the Manus session to your GitHub repo
   • In the new Manus task, provide the repository URL and a personal access token
   • Manus can clone the repo locally and work from that updated baseline

When transferring progress, provide clear instructions in the new task session explaining how Manus should utilize the transferred assets to continue the overall project.

Preparation and Efficiency

• Perform preliminary work, data cleaning, outlining, or asset creation outside of Manus using other tools when possible
• Provide Manus with well-structured initial materials, a clear outline, or foundational code
• Use external tools for preparatory steps, then bring those prepared materials into Manus
• Leverage Manus for tasks it excels at: integrating diverse components, executing complex steps, finishing tasks, and grasping the 'big picture'

Resource Efficiency Guidelines