Maximizing Performance
Best practices for efficient development with Same.
Follow these strategies to get the best results and manage costs effectively when using Same.
1. Start New Chats Frequently
Treat each chat as a single task or feature.
Benefits:
- Cost Control: Prevents context windows from becoming too large, reducing token usage.
- Accuracy: Keeps Same focused on the current task without confusion from old context.
- Debugging: Makes it easier to isolate issues within a shorter history.
When to start a new chat:
- After completing a feature.
- When switching to a significantly different task.
- If the chat history becomes very long or Same seems confused.
Use the “New Chat” button ( icon, top-right in chat panel) to start fresh.
2. Provide Specific Context
Help Same understand exactly what you need.
Use '@ Add context'
Click the @ Add context button in the chat input to: - Select specific
project files for Same to read or modify. - Include summaries of relevant
previous chats.
Provide Links
Share URLs to documentation, examples, or inspiration sites. Same can browse these for information.
Use the '@ Add context' button to include files or summaries in your prompt.
Targeted context is more efficient than asking Same to search broadly. See Build basics.
3. Use Version Control Effectively
If Same makes a mistake:
- Find the last good state: Look through the message history or use the Version History panel (clock icon ) to find the checkpoint before the error.
- Restore checkpoint: Click “Restore checkpoint” next to the message/action to preview that state in the workbench.
- Revert (if needed): If the preview is correct, click “Revert to checkpoint”. This resets the project to that checkpoint (irreversible).
Use 'Restore checkpoint' and 'Revert to checkpoint' to manage project history.
Reverting to a known good state is often faster than trying to fix multiple errors. See the Version control guide.
Maximizing Performance
Best practices for efficient development with Same.
Follow these strategies to get the best results and manage costs effectively when using Same.
1. Start New Chats Frequently
Treat each chat as a single task or feature.
Benefits:
- Cost Control: Prevents context windows from becoming too large, reducing token usage.
- Accuracy: Keeps Same focused on the current task without confusion from old context.
- Debugging: Makes it easier to isolate issues within a shorter history.
When to start a new chat:
- After completing a feature.
- When switching to a significantly different task.
- If the chat history becomes very long or Same seems confused.
Use the “New Chat” button ( icon, top-right in chat panel) to start fresh.
2. Provide Specific Context
Help Same understand exactly what you need.
Use '@ Add context'
Click the @ Add context button in the chat input to: - Select specific
project files for Same to read or modify. - Include summaries of relevant
previous chats.
Provide Links
Share URLs to documentation, examples, or inspiration sites. Same can browse these for information.
Use the '@ Add context' button to include files or summaries in your prompt.
Targeted context is more efficient than asking Same to search broadly. See Build basics.
3. Use Version Control Effectively
If Same makes a mistake:
- Find the last good state: Look through the message history or use the Version History panel (clock icon ) to find the checkpoint before the error.
- Restore checkpoint: Click “Restore checkpoint” next to the message/action to preview that state in the workbench.
- Revert (if needed): If the preview is correct, click “Revert to checkpoint”. This resets the project to that checkpoint (irreversible).
Use 'Restore checkpoint' and 'Revert to checkpoint' to manage project history.
Reverting to a known good state is often faster than trying to fix multiple errors. See the Version control guide.