Blog
Essay
Less benchmarks, better chatbots.
Models keep getting smarter. The chat around them still looks like 2022. Most people feel convenience, not a few points on a benchmark.
four small ideas. try them, they are live.
1
Tabs
One chat per browser tab is not enough.
Working across chats should feel like working across tabs.
U
Hello! How can I help you today?
I'd like to learn about the differences between chat interfaces
Great question! The main difference is how new conversations are handled. Try clicking "New chat" to see how this interface works compared to traditional single-chat systems.
2
Forks
Context is everything in a chat.
Branch from any message instead of starting over.
U
Hello! I demonstrate forking with tabs.
What happens when I fork a message here?
When you fork any message, it creates a new tab with all previous messages intact! You can explore different conversation paths without losing history.
So I can branch conversations at any point?
Exactly! Hover over any message and click the fork button to create a new conversation branch in a new tab. Try it!
3
Files
Upload once, reference anywhere with @.
One shared place for the files you work with.
U
Hello! I can help you reference files using the @ symbol. Click the Files tab to see available files, then use @ in chat to reference them.
Select a file to reference (use arrow keys):
4
Search
Search what was said, not just chat titles.
The real value is inside the conversation.
U
Hey! I uploaded the project overview document for our Q3 planning.
Attached files:
📄project-overview.pdf
Jan 15, 10:00 AM
Great! I can see the project overview. The timeline looks ambitious but achievable.
Jan 15, 10:05 AM
Can you review these design mockups? They show the new user interface concepts.
Attached files:
🖼️design-mockups.png
Jan 15, 11:30 AM
The mockups look excellent! The color scheme and layout are very user-friendly.
Jan 15, 11:45 AM
I also have the detailed requirements document. This covers all the technical specifications.
Attached files:
📝requirements.docx
Jan 15, 02:20 PM
Perfect! Let me analyze the requirements. I notice some API integration requirements that we should discuss.
Jan 15, 02:30 PM
Here's the main JavaScript file with the core logic. Can you help me optimize it?
Attached files:
📜main.js
Jan 16, 09:15 AM
I've reviewed the JavaScript code. There are several optimization opportunities, especially in the data processing functions.
Jan 16, 09:30 AM
Also sharing the API documentation for reference.
Attached files:
📄api-docs.pdf
Jan 16, 03:45 PM
The API documentation is comprehensive. I can see the authentication flow and all the endpoints we'll need.
Jan 16, 04:00 PM
I've been working on some utility functions. These should help with data processing.
Attached files:
📜utils.js
Jan 17, 01:20 PM
The utility functions look great! They'll definitely improve code reusability.
Jan 17, 01:35 PM
Finally, here are the user stories document with all the acceptance criteria.
Attached files:
📝user-stories.docx
Jan 18, 10:10 AM
Excellent! The user stories are well-structured and will guide our development process effectively.
Jan 18, 10:25 AM
It now pays more to improve the experience than the model.