Skip to content

Update agent notifications support for Auggie - #475

Open
tkossak wants to merge 4 commits into
warpdotdev:mainfrom
tkossak:patch-1
Open

Update agent notifications support for Auggie#475
tkossak wants to merge 4 commits into
warpdotdev:mainfrom
tkossak:patch-1

Conversation

@tkossak

@tkossak tkossak commented Aug 5, 2026

Copy link
Copy Markdown

Summary

Auggie does support agent notifications in warp - I marked it so in the feature table.

Related issues

Closes #576

Validation

docs only

Screenshots

Follow-ups

@cla-bot

cla-bot Bot commented Aug 5, 2026

Copy link
Copy Markdown

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 @tkossak 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 @cla-bot check to trigger another check.

@vercel

vercel Bot commented Aug 5, 2026

Copy link
Copy Markdown

@tkossak is attempting to deploy a commit to the warpdotdev Team on Vercel.

A member of the Team first needs to authorize it.

@oz-for-oss

oz-for-oss Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@tkossak

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tkossak

Every PR must be linked to a same-repo issue before Oz can review it.

Next step: open or find a same-repo issue describing this change, then link it to this PR by adding Closes #123 to the PR description (or using the "Development" sidebar on GitHub). A maintainer will mark the issue ready-to-implement when it is ready. Once it is marked, comment /oz-review to re-trigger review.

See the contribution guidelines for the full readiness model.

Powered by Oz

@tkossak

tkossak commented Aug 5, 2026

Copy link
Copy Markdown
Author

@cla-bot check

@cla-bot cla-bot Bot added the cla-signed label Aug 5, 2026
@cla-bot

cla-bot Bot commented Aug 5, 2026

Copy link
Copy Markdown

The cla-bot has been summoned, and re-checked this pull request!

@hongyi-chen

Copy link
Copy Markdown
Collaborator

Thanks!

@hongyi-chen
hongyi-chen enabled auto-merge (squash) August 5, 2026 19:25
@warp-agent-staging

Copy link
Copy Markdown
Contributor

/oz-review

1 similar comment
@hongyi-chen

Copy link
Copy Markdown
Collaborator

/oz-review

@oz-for-oss

oz-for-oss Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@hongyi-chen

I'm re-reviewing this pull request in response to a review request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This docs PR updates the third-party CLI agents overview feature table to mark Auggie as supporting agent notifications. The change is small, but it leaves the published docs internally inconsistent about Auggie notification support.

Concerns

  • The table now says Auggie supports agent notifications, while the unchanged note later on the same page still says Auggie does not support notifications yet. The dedicated Agent Notifications page also omits Auggie from the supported third-party agents and setup instructions.

Verdict

Found: 0 critical, 1 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

|---|---|---|---|---|---|---|---|---|---|---|
| Rich input editor (`Ctrl-G`) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Agent notifications | ✓ | ✓ | ✓ | ✗ | | ✗ | ✗ | ✗ | ✗ | ✗ |
| Agent notifications | ✓ | ✓ | ✓ | ✗ | | ✗ | ✗ | ✗ | ✗ | ✗ |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ [IMPORTANT] This flips only the table, but the note below this table still says Auggie doesn't support notifications yet, and /agents/capabilities/agent-notifications/ still omits Auggie from the supported agents/setup instructions. Update the supporting text/setup docs in the same PR or keep Auggie as here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: mark Auggie as supporting agent notifications in CLI agents overview

2 participants