docs(agenteye): agents can start the sign-in now

[NiveditJain]

Why

docs/agenteye/cli-and-agents.mdx told readers:

Log in yourself first: the skill cannot complete the emailed-code login for you.

That is no longer true. FailproofAI/agenteye#477 adds device sign-in, so a coding agent can start the login itself and hand the user a link to approve.

What changed

Rewrote that paragraph and the one after it:

• The agent starts the sign-in and gives the user a link plus a short code. The user opens it, checks the code matches their terminal, chooses what the agent may do, and approves. No code is copied out of an inbox, and the agent never sees one.
• Added what the user controls: the approval screen is pre-selected with what the agent asked for and limited to what the user holds themselves, and every signed-in browser and agent can be seen and ended at any time.
• Sharpened the existing note about the "are you sure?" prompt not firing for an agent — it is a convention, whereas the approved permissions are enforced.

Public-docs bar

Value and contract only. No mention of the grant type, the endpoints, the token or code lifetimes, the storage, the rate limits, or how the scoping is enforced — that depth lives in the enterprise set (enterprise-docs/security.md), written separately rather than copied.

Counterpart to FailproofAI/agenteye#477. Once this merges, bump-platform-submodule.yml pushes the submodule pointer to AgentEye's main automatically — no bump PR needed there.

🤖 Generated with Claude Code

https://claude.ai/code/session_013uML35iHo8GmymozNwCrJD

[coderabbitai]

Warning

Review limit reached

@NiveditJain, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 90c76aa0-c833-4966-876b-3945638f7e7c

📥 Commits

Reviewing files that changed from the base of the PR and between 41b14d6 and 01c3425.

📒 Files selected for processing (2)

• CHANGELOG.md
• docs/agenteye/cli-and-agents.mdx

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}