fix(ai): inject .ai/progress.md as project context in AI sessions#10344
fix(ai): inject .ai/progress.md as project context in AI sessions#10344kinzirva wants to merge 2 commits into
Conversation
Closes warpdotdev#10342 When a project contains .ai/progress.md, the current and next task are automatically injected into every AI session whose pwd is inside that project. Task status is auto-derived from git commit history, keeping context in sync across all Warp windows without manual maintenance. - Add app/src/ai/project_progress.rs: parser, git-log deriver, context formatter - Inject progress context via AIAgentContext::ProjectRules in context_model.rs::pending_context() - Add specs/GH10342/product.md and tech.md Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @kinzirva on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment |
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
github-actions
Bot
added
the
external-contributor
|
@cla-bot check |
|
The cla-bot has been summoned, and re-checked this pull request! |
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
Overview
This PR adds client-side project progress context from .ai/progress.md and injects it into AI sessions as ProjectRules, with optional .ai/ctx files and git-log status derivation.
Concerns
- Progress lookup only checks the terminal's exact working directory, so sessions opened in subdirectories of a project do not receive the promised project-wide context.
- Empty or fully unparsable
progress.mdfiles still inject a[CURRENT] (no task in progress)block instead of skipping context as specified.
Verdict
Found: 0 critical, 2 important, 0 suggestions
Request changes
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Address oz-for-oss review comments on warpdotdev#10344: - ProjectProgressContext::load now walks ancestors of the start dir (capped at 30) so sessions in subdirectories of the project still pick up .ai/progress.md. - When progress.md is empty or has no parseable task lines, load returns None instead of injecting a [CURRENT] (no task in progress) placeholder. Adds three tests covering both behaviours plus the not-found case.
|
Thanks for the review — addressed both in f05c4a3:
Added three tests covering the new behaviour. |
|
@oz-for-oss please re-review — commit f05c4a3 addresses both items. |
kinzirva
changed the title
1 participant
Closes #10342
When a project contains .ai/progress.md, the current and next task are automatically injected into every AI session whose pwd is inside that project. Task status is auto-derived from git commit history, keeping context in sync across all Warp windows without manual maintenance.
Description
Linked Issue
ready-to-specorready-to-implement.Testing
./script/runScreenshots / Videos
Agent Mode