Manus

The Manus task ID to check. Use the task_id returned in structured output from an initiate_* tool (or a task ID provided by the user / visible in the Manus task link). Use this to check whether the task is pending, running, completed, or failed.

Provide comprehensive requirements for the mobile app. Include (as applicable): - App purpose + target users - Key screens with content-specific details (what data/content appears on each screen) - Navigation structure: how users move between screens - User flows: Step-by-step paths for main actions (e.g., 'User taps item → Detail screen → Add to cart → Checkout sheet') - Core features: CRUD flows, media, maps, chat, etc. - Integrations: payments, analytics, wearable/health APIs, push notifications, etc. - Design philosophy: iOS-native feel or custom design approach - Branding: App name, specific brand colors (hex codes), light/dark mode, accessibility needs - App icon: Description of desired icon design - Data persistence: Specify if data should sync across devices or stay local - Important: Do NOT specify the tech stack, frameworks, or implementation approach (e.g., "use React Native", "use Expo", "use Firebase") Example: 'Build a fitness tracker app called Fitness Tracker. Screens: onboarding (3 screens explaining features), dashboard (today's summary, quick-start workout button), workout logging (exercise list, timer, reps/sets input), history (calendar view, workout cards), progress charts (weight/reps over time), profile (user settings, goals). Main navigation between Dashboard, History, and Profile. User flow: Dashboard → Start Workout → Select exercises → Log sets → Complete → Save to history. Dark mode with iOS-native design. Brand colors: #1a1a1a background, #00d4aa primary, #ffffff text. App icon: dumbbell icon in minimalist style. Optional: social sharing, push reminders for scheduled workouts. Data stays on device only.'

Provide comprehensive requirements for the research. Be explicit about scope and outputs. Include (as applicable): - Research question(s) and what decision or understanding it should support - Audience and desired depth (executive overview vs deep technical analysis) - Scope boundaries: what to include/exclude, and key subtopics to explore - Time range and geography (if relevant) - Preferred sources: academic papers, industry reports, news, primary sources, government/policy docs; sources to avoid - Output format: structure, sections, tables, comparison matrices, recommendations, key takeaways - Citation requirements: whether to include links/citations, and preferred style/placement Example: 'Research the top 10 AI healthcare startups (last 3 years, US/EU focus). Cover: (1) company profiles and core technologies, (2) clinical applications and differentiators, (3) funding history and major investors, (4) regulatory and compliance aspects, (5) key challenges and future outlook. Target audience: healthcare investors and executives. Output: executive summary + detailed profiles of 10 startups + comparison table + risks assessment + strategic recommendations. Include citations with links to primary/credible sources.'

Provide comprehensive requirements for the slide deck. Include (as applicable): - Topic + goal: what the deck is for and the key message - Target audience + context (e.g., internal execs, customers, students) - Desired slide count - Preferred structure (outline / sections) - Tone and style (formal/casual, minimal/visual) - Visual aesthetic: Specify a design movement or archetype (e.g., Swiss/Brutalist/Memphis/Editorial Magazine/Art Deco/Minimalist Japanese/Bauhaus) - avoid generic terms like 'modern' or 'clean' - Color palette: Specific hex codes for background, title, body text, and 1-2 accent colors - Typography: Font family and sizes for different heading levels and body text - Content requirements: key points, must-include facts, data with sources, and exclusions - Data/visuals: charts/diagrams desired, and any sources to use Example: 'Create a 10-slide deck for a corporate audience explaining renewable energy adoption. Aesthetic: Editorial Magazine style with bold typography and asymmetric layouts. Colors: #1a1a1a background, #ffffff text, #0066ff accent. Font: Space Grotesk for headings (64px), Inter for body (20px). Include 2 charts with sourced stats (last 3 years) and a SWOT slide. Use real data only.'

Provide comprehensive requirements for the video. Include (as applicable): - Topic/story + goal + target audience - Duration target - Aspect ratio: landscape (16:9), portrait (9:16), or square (1:1) - Style: animated, motion graphics, cinematic, product demo, etc. - Scene breakdown: Describe each shot/scene with detailed visual descriptions (camera movement, lighting, subject, action, etc.) - Visual consistency: For multi-shot videos, describe reference images or visual style to maintain across shots - Script/narration: If voiceover is needed, provide script or ask Manus to write one (tone, reading level, voice type preference) - Pacing: Describe transitions, rhythm, and timing between scenes - Branding: logo, colors, typography, intro/outro, call-to-action Example: 'Create a 30-second product demo video for a smart home device. Aspect ratio: 16:9 landscape. Style: Modern cinematic with smooth camera movements. Scene 1 (0-10s): Close-up of device on minimalist table, warm lighting, camera slowly zooms in. Scene 2 (10-20s): Hand taps device screen, interface lights up with blue glow, camera circles around. Scene 3 (20-30s): Wide shot of modern living room with device in context, evening ambient lighting. Maintain consistent modern minimal style with warm lighting across all shots. Include gentle background music (ambient electronic). End with product logo fade-in.'

Provide comprehensive requirements for the website. Include (as applicable): - Purpose + target audience - Pages/routes: required pages and key sections per page - Copy/content: provide text, placeholders, or ask Manus to draft (specify desired tone) - Design philosophy: Specify a unique aesthetic approach (e.g., Swiss Typography, Brutalist, Memphis Design, Editorial Magazine, Art Deco, Parametric) - avoid generic 'modern/clean/minimal' - Branding: name/logo, brand colors (with specific hex codes), typography, light/dark mode - Layout paradigm: Describe unique structural approach - Signature elements: 2-3 distinctive visual motifs - Animation guidelines: How animations reflect the design ethos - Features (optional): forms, user accounts, payments, content management, search, analytics, SEO, localization, AI features, voice input, image generation, file uploads - Integrations (optional): APIs, third-party services, tracking pixels - Important: Do NOT specify the tech stack, frameworks, hosting, or implementation approach (e.g., "use Next.js", "deploy on Vercel", "use Tailwind") Example: 'Build a SaaS landing site with Home, Pricing, Docs, and Contact pages. Design philosophy: Editorial Magazine style with bold typography, asymmetric layouts, and brutalist color blocks. Colors: #0a0a0a background, #ffffff text, #ff4444 accent. Fonts: Space Grotesk for headings, Inter for body. Include diagonal section transitions, a pricing comparison table, email capture form, and basic SEO. Draft concise copy in a confident, technical tone.'

Log level: error, warn, or info

The log message

Optional additional context