> ## Documentation Index > Fetch the complete documentation index at: https://beta-docs.replo.app/llms.txt > Use this file to discover all available pages before exploring further. # Tasks > Schedule prompts to run in the background, on a one-off or recurring basis. export const TryPromptButton = ({prompt, imageSrc, imageAlt = "Template preview", imageStyles = {}, buttonCta = "Build in Replo"}) => { const [isLoading, setIsLoading] = useState(false); const [error, setError] = useState(null); const API_BASE = "https://api.replo.app"; const APP_URL = "https://dashboard.replo.app"; const LoaderIcon = ; const ChevronIcon = ; async function postJSON(url, body, headers = {}, timeoutMs = 120000) { const controller = new AbortController(); const timeoutId = setTimeout(() => controller.abort(), timeoutMs); try { const response = await fetch(url, { method: "POST", headers: { "Content-Type": "application/json", ...headers }, body: JSON.stringify(body ?? ({})), signal: controller.signal }); const responseText = await response.text(); if (!response.ok) throw new Error(`API Error: ${response.status}`); return responseText ? JSON.parse(responseText) : {}; } finally { clearTimeout(timeoutId); } } async function handleTryPrompt(event) { event.preventDefault(); event.stopPropagation(); setIsLoading(true); setError(null); try { const body = { prompt, file: null }; const {seed} = await postJSON(`${API_BASE}/api/v1/marketing/issue-marketing-site-jwt`, body); if (!seed) throw new Error("No seed returned from API"); const url = new URL(APP_URL); url.searchParams.set("type", "agent"); url.hash = `seed=${encodeURIComponent(seed)}`; window.open(url.toString(), "_blank"); setIsLoading(false); } catch (caughtError) { console.error("Failed to generate prompt:", caughtError); const message = caughtError instanceof Error ? caughtError.message : null; setError(message ?? "Something went wrong. Please try again."); setIsLoading(false); } } return
{} {imageSrc && {imageAlt}} {}
{} {} {error &&
{error}
}
; }; export const Screenshot = ({src, altText, width, shadow = true}) => { const generateAltText = imageSrc => { if (!imageSrc) return "Screenshot"; const filename = imageSrc.split("/").pop() ?? ""; const nameWithoutExt = filename.replace(/\.[^/.]+$/, ""); const readable = nameWithoutExt.replace(/[-_]/g, " ").replace(/\b\w/g, char => char.toUpperCase()); return readable === "" ? "Screenshot" : readable; }; const finalAltText = altText ?? generateAltText(src); const imageWidth = width ? `${width}px` : "100%"; return
{} {}
{finalAltText}
; }; Tasks let Replo do work on a schedule, in the background. You write a prompt once, choose when it should run, and Replo carries it out on its own, whether that is once next Tuesday or every Monday morning. It is how you turn recurring work, like a weekly performance report, into something that happens automatically. A task is just a prompt with a schedule attached. Anything you would ask Replo to do once, you can ask it to do on repeat: ```text theme={null} Every Monday at 9am, summarize last week's traffic, revenue, and best-converting pages, and flag anything that dropped. ``` ```text theme={null} Every Friday, check my published pages for broken links and slow images, and report what you find. ``` You can reach Tasks from the **+** in the tab bar or the Cmd+K menu. ## The three views Tasks opens with three tabs: * **Home** shows what is happening now: anything scheduled or completed today, a view of the week ahead, and any runs that failed and need a look. That is the view pictured above. * **Schedule** is a calendar of upcoming runs. * **History** is the full log of past runs. **Schedule** shows your upcoming runs on a calendar, which you can view by month, week, or day. **History** is the full log of past runs, which you can filter by outcome (all, succeeded, failed, or running). ## Create a task Click **New task** from any view. You can also click a day in the week or calendar views to start a task scheduled for that day. Give the task a title and write the prompt you want Replo to run, the same way you would ask it in chat. Pick an emoji to make it easy to spot. Set the date and time, then choose how it repeats: **Does not repeat**, **Daily**, **Every weekday**, **Weekly** on a chosen day, or **Monthly**. A schedule preview shows you the next runs before you save. ## Run, review, and adjust * **Run now.** From a task, run it immediately without waiting for its schedule, which is handy for testing the prompt. * **Review each run.** Every run is recorded in the task's history with its status (queued, running, succeeded, or failed). Open **View chat** on any run to see the full Replo session for that run, exactly what it did and produced. * **Edit or delete.** Change a task's prompt or schedule whenever your needs change, or delete it when you are done. When a run finishes, its work lives in a normal Replo session. The task detail view shows its **Run now** and **Edit task** actions, the next run, repeat schedule, and run history alongside the report it produced, here a full traffic, revenue, and top-pages summary you can open and read. Tasks you have coming up also surface on [Home](/navigating-replo#home) through the **Tasks** widget, so you can see what Replo will do next without opening the app. ## Related A growth loop powered by scheduled reports. How task runs show up in your chat history.