<head>
<script type=“application/ld+json”>
{{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does setting a goal change my mode?", "acceptedAnswer": {"@type": "Answer", "text": "Goals always run in Build mode, so if the mode picker is on Plan when you send a /goal message, RShift Sites switches the picker to Build, and it stays on Build until you change it. The goal itself applies only to the message you send it with: your next message is a regular message, in the mode the picker shows. The same is true for a project you create from the dashboard with a /goal prompt: the goal covers only that first message, and the editor opens in Build mode like any new project."}}, {"@type": "Question", "name": "Why did my /goal message send as a normal message?", "acceptedAnswer": {"@type": "Answer", "text": "RShift Sites was already working on a regular message when you sent it. You can't set a goal while a message is in progress, and a notice above the chat input warns you before you send. The message is still sent, but /goal has no effect and stays in the message as ordinary text. If RShift Sites is working on a goal instead, your message joins that goal as a follow-up."}}, {"@type": "Question", "name": "Do I need to type /goal again when I retry a failed message?", "acceptedAnswer": {"@type": "Answer", "text": "No. If a message you sent as a goal fails and you retry it from the project chat, the retried message is sent as a goal again."}}, {"@type": "Question", "name": "How much does a goal cost?", "acceptedAnswer": {"@type": "Answer", "text": "A goal is billed on the work RShift Sites does, and it costs noticeably more than a regular Build mode message, for two reasons: the same work uses more credits, and a goal involves more work, because RShift Sites keeps working until the goal is achieved. Credit check-ins still pause the work at your check-in level, and the stop button stops it at any time."}}, {"@type": "Question", "name": "How do I recognize a goal in the chat history?", "acceptedAnswer": {"@type": "Answer", "text": "Messages you sent with /goal are marked Goal in the project chat, so you can tell them apart from your other messages."}}]}}
</script>
</head>
A goal is a Build mode message that RShift Sites keeps working on until the goal is achieved. You can set one on any message: the first prompt of a new project or any message in an existing project. Set a goal for a large task that you want finished completely, such as a feature that spans several parts of your app.
A goal can take hours to finish and use a large number of credits, so use it for work where a complete result matters more than speed or cost.
How RShift Sites works on a goal
A goal changes how RShift Sites works on the message:
- RShift Sites works until the goal is achieved, for up to 10 hours on the one message, and uses the final half hour to finish what is in progress and summarize what is done.
- RShift Sites doesn’t pause to ask questions about the work. It makes routine decisions itself, and stops early only when it needs something that only you can provide, such as access to another service. Because of this, write the goal so RShift Sites can finish on its own.
- RShift Sites still checks in about cost. Like any long-running message, a goal pauses when it crosses your credit check-in level and asks whether to continue. Choose Continue and RShift Sites resumes where it left off.
- RShift Sites builds the finished version. It completes what you asked for, rather than delivering a first version for you to review and refine.
- You can still guide the work. Send follow-up messages to adjust the direction, and they become part of the goal. Follow the progress in the activity cards, or click the stop button to stop the work.
Set a goal
You set a goal in the message itself, with the /goal command. Goal is listed with the skills built by RShift Sites, and you add it the same way you add a skill:
Add the command to your message
Type /goal anywhere in your message, or type / and pick Goal from the Skills list. The same list is in the Chat actions menu, the + button next to the chat input, under Add context → Skills. The command appears as a Goal tag in your message, and a banner above the chat input confirms the goal: “RShift Sites will work until your goal is achieved. This might take hours and use a large number of credits.” Write the rest of the message as a description of the goal. A message with /goal and nothing else doesn’t send.
Send the message
RShift Sites removes the /goal command from the message text, and the sent message is marked Goal in the project chat so you can recognize it later.
/goal Refactor the checkout flow to support saved payment methods, update the database schema, and add tests for the new endpoints.The name goal is reserved for this command, so you cannot create a skill named goal.
Write a goal RShift Sites can finish on its own
RShift Sites doesn’t pause to ask you questions during a goal, so the message needs to include everything RShift Sites would otherwise ask about:
- What a finished result looks like. Describe the parts you expect, such as the pages, flows, or data involved, and what the finished app should do.
- The decisions you care about. RShift Sites decides anything you leave open, so state how you want the result to look and behave, and the edge cases it must handle.
- Access to other services. If the work involves other services, set up the connectors and secrets it needs before you send the goal. RShift Sites stops early if it needs access that only you can grant.
A goal still pauses at your credit check-in level like any long-running message. If you want fewer pauses on a large goal, adjust the level in account settings before you start.
Goals run in Build mode
Goals always run in Build mode. If the mode picker is on Plan when you send a /goal message, RShift Sites switches the picker to Build, and it stays on Build until you change it. If the message fails to send, the picker stays on Plan.
The goal applies only to the message you send it with: your next message is a regular message, in the mode the picker shows.
When you can’t set a goal
You can’t set a goal while RShift Sites is already working. What happens to a /goal message you send during that time depends on what RShift Sites is working on:
- While RShift Sites works on a regular message, no goal is set. A notice above the chat input warns you first, and the message is sent as a regular message: the
/goalcommand has no effect and stays in the message as ordinary text. - While RShift Sites works on a goal, your message joins that goal as a follow-up and becomes part of the work toward the same goal. No notice appears.
What a goal costs
A goal is billed on the work RShift Sites does, and it costs noticeably more than a regular Build mode message, for two reasons: the same work uses more credits, and a goal involves more work, because RShift Sites keeps working until the goal is achieved. You are charged for all of that work, from start to finish.
Credit check-ins still apply: the work pauses when it crosses your check-in level, and choosing Finish up ends the goal early, with RShift Sites finishing the work in progress and stopping. The stop button stops the work at any time, and you are only charged for the work completed up to that point. Check your credit balance before you set a large goal. The cost controls for Build mode requests all apply to goals too.
FAQ
Does setting a goal change my mode?
Goals always run in Build mode, so if the mode picker is on Plan when you send a /goal message, RShift Sites switches the picker to Build, and it stays on Build until you change it. The goal itself applies only to the message you send it with: your next message is a regular message, in the mode the picker shows. The same is true for a project you create from the dashboard with a /goal prompt: the goal covers only that first message, and the editor opens in Build mode like any new project.
Why did my /goal message send as a normal message?
RShift Sites was already working on a regular message when you sent it. You can’t set a goal while a message is in progress, and a notice above the chat input warns you before you send. The message is still sent, but /goal has no effect and stays in the message as ordinary text. If RShift Sites is working on a goal instead, your message joins that goal as a follow-up.
Do I need to type /goal again when I retry a failed message?
No. If a message you sent as a goal fails and you retry it from the project chat, the retried message is sent as a goal again.
How much does a goal cost?
A goal is billed on the work RShift Sites does, and it costs noticeably more than a regular Build mode message, for two reasons: the same work uses more credits, and a goal involves more work, because RShift Sites keeps working until the goal is achieved. Credit check-ins still pause the work at your check-in level, and the stop button stops it at any time.
How do I recognize a goal in the chat history?
Messages you sent with /goal are marked Goal in the project chat, so you can tell them apart from your other messages.