AI Chat
AIDEN uses the same core chat experience across the product.
The main difference is not a completely different chat system. The difference is context.
That means the chat feels different depending on where you use it:
- project chat carries project-level context
- story chat stays anchored to one story and its spec
- agent chat reflects the role and instructions of that agent
What AI Chat actually is
AI Chat is the working conversation layer inside AIDEN.
It helps you:
- ask questions about the current work
- plan a task
- refine a spec
- review implementation choices
- move faster without leaving the product
Why context matters more than chat type
In many AI tools, every conversation feels detached from the work.
AIDEN is stronger when the conversation stays close to the thing you are doing. That is why context matters so much:
- project context helps with broader planning
- story context helps with focused execution
- agent context helps a specialist stay in character and on task
The UI can feel similar while the working context stays meaningfully different.
The practical mental model
Do not think of AIDEN as having completely separate chat products. Think of it as one AI chat layer that becomes more useful when attached to the right context.
That is what keeps conversations closer to real software work instead of turning everything into one giant generic thread.
Best practice
Use the chat closest to the work you want to move:
- use project context for broader planning
- use story context for scoped implementation and spec work
- use agent context when a specialist role adds value
The closer the context matches the task, the better the output usually gets.