You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when using q chat in a project directory, users need to manually provide context about the project. However, most repositories already contain this information in their README.md files.
CLI CHAT should automatically detect and read the README.md file (if present) in the current working directory when initialized.
This would:
Provide immediate project context without manual input
Help generate more relevant and project-aware responses
Save time by eliminating the need to paste README contents manually.
Implementation could:
Check for README.md existence on startup
Parse markdown content
Use content as initial context for the conversation
Allow users to opt-out via config setting
Support alternative README file formats (README.txt, README, etc.)
Benefits
Improved developer experience
More contextual responses
Faster project onboarding
Better alignment with repository's documented goals and structure
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Currently, when using
q chatin a project directory, users need to manually provide context about the project. However, most repositories already contain this information in their README.md files.CLI CHAT should automatically detect and read the README.md file (if present) in the current working directory when initialized.
This would:
Implementation could:
Benefits
All reactions