Skip to content

Audit website claims against current runtime support - #1846

Open
simple-agent-manager[bot] wants to merge 2 commits into
mainfrom
sam/weekly-website-claims-audit-9r8nzc
Open

Audit website claims against current runtime support#1846
simple-agent-manager[bot] wants to merge 2 commits into
mainfrom
sam/weekly-website-claims-audit-9r8nzc

Conversation

@simple-agent-manager

Copy link
Copy Markdown
Contributor

Summary

@raphaeltm weekly website claims audit for apps/www/. I checked the landing page components, docs overview/concepts pages, roadmap page, and the implementation sources that define agents, cloud providers, runtimes, orchestration, deployments, notifications, and collaboration.

Area checked Code/source checked Result Change
Supported agents packages/shared/src/agents.ts, packages/shared/src/agent-install-manifest.json, harness capabilities Six public agents still match code: Claude Code, OpenAI Codex, Gemini CLI, Mistral Vibe, OpenCode, Amp. None
Supported providers apps/api/src/schemas/credentials.ts, apps/api/src/schemas/workspaces.ts, provider-related API/UI references Public provider list still matches code: Hetzner, Scaleway, Vultr, Infomaniak, DigitalOcean, UpCloud, GCP. None
Runtime/user journey claims apps/api/src/db/schema.ts, apps/web/src/components/agent-profiles/ProfileFormDialog.tsx, docs concepts runtime section Homepage copy still implied every chat required cloud VM/devcontainer. Code supports Instant cf-container profiles and hosted/platform compute paths. Updated Hero, Features, How It Works, and Comparison copy to describe Instant containers or cloud VMs.
Feature descriptions Routes/services/components for chat, notifications, forking, triggers, runtime config, app deployments Described capabilities remain implemented. None
Comparison table Same agent/provider/runtime sources Provider/agent rows were accurate except runtime row needed Instant path included. Updated SAM “Your code runs on” cell.
Roadmap status apps/api/src/db/schema.ts, deployment services/routes/UI, project membership schema/UI, CLI package, trigger schemas Complete/Planned statuses reviewed; no shipped major item found incorrectly left as Planned besides no AWS support still planned. None
Docs overview/concepts/roadmap apps/www/src/content/docs/docs/overview.mdx, concepts.mdx, reference/roadmap.md Docs already describe Instant vs VM and hosted compute accurately. None

Verification

  • pnpm --filter @simple-agent-manager/www build

Notes

  • No blog posts were changed.
  • No structural layout/navigation changes were made.
  • Pre-existing local .codex/config.toml modification was not committed.

Auto-committed by SAM on agent completion.
@sonarqubecloud

Copy link
Copy Markdown

@codspeed-hq

codspeed-hq Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Merging this PR will not alter performance

✅ 6 untouched benchmarks


Comparing sam/weekly-website-claims-audit-9r8nzc (4b04b14) with main (35c5732)

Open in CodSpeed

@raphaeltm

Copy link
Copy Markdown
Owner

@coderabbitai please help me understand: why didn't you automatically review this pr?

@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="raphaeltm/simple-agent-manager"
pr_number="1846"

echo '=== PR metadata ==='
gh pr view "$pr_number" --repo "$repo" \
  --json number,state,isDraft,createdAt,updatedAt,author,baseRefName,headRefName,labels,reviewRequests,statusCheckRollup \
  --jq '{number,state,isDraft,createdAt,updatedAt,author:.author.login,baseRefName,headRefName,labels:[.labels[].name],reviewRequests:[.reviewRequests[].login],checks:[.statusCheckRollup[]? | {name:.name,conclusion:.conclusion,status:.status}]}'

echo '=== Recent PR timeline events ==='
gh api "repos/$repo/issues/$pr_number/timeline" \
  -H 'Accept: application/vnd.github+json' \
  --paginate \
  --jq '.[] | select(.event == "labeled" or .event == "unlabeled" or .event == "ready_for_review" or .event == "converted_to_draft" or .event == "review_requested" or .event == "head_ref_force_pushed" or .event == "committed" or .event == "closed" or .event == "reopened") | {event,created_at,actor:(.actor.login // null),label:(.label.name // null),commit_id:(.commit_id // null)}'

Length of output: 3679


⚙️ CodeRabbit configuration inspected

Length of output: 5450


🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="raphaeltm/simple-agent-manager"
pr_number="1846"
head_sha=$(gh pr view "$pr_number" --repo "$repo" --json headRefOid --jq '.headRefOid')

echo '=== Pull request state and author ==='
gh api "repos/$repo/pulls/$pr_number" \
  --jq '{number,created_at,updated_at,draft,user:{login:.user.login,type:.user.type},author_association}'

echo '=== Pull request reviews ==='
gh api "repos/$repo/pulls/$pr_number/reviews" --paginate \
  --jq '.[] | {submitted_at,state,user:(.user.login // null),body}'

echo '=== Pull request issue comments with CodeRabbit mentions ==='
gh api "repos/$repo/issues/$pr_number/comments" --paginate \
  --jq '.[] | select((.user.login | ascii_downcase | contains("coderabbit")) or (.body | ascii_downcase | contains("coderabbit"))) | {created_at,user:.user.login,body}'

echo '=== Check runs from CodeRabbit ==='
gh api "repos/$repo/commits/$head_sha/check-runs" \
  -H 'Accept: application/vnd.github+json' --paginate \
  --jq '.check_runs[] | select((.app.slug // "" | ascii_downcase | contains("coderabbit")) or (.name | ascii_downcase | contains("coderabbit"))) | {name,status,conclusion,started_at,completed_at,app:(.app.slug // null),details_url}'

echo '=== Pull request timeline: state-changing events ==='
gh api "repos/$repo/issues/$pr_number/timeline" \
  -H 'Accept: application/vnd.github+json' --paginate \
  --jq '.[] | select(.event == "opened" or .event == "ready_for_review" or .event == "converted_to_draft" or .event == "synchronize" or .event == "review_requested" or .event == "committed") | {event,created_at,actor:(.actor.login // null),commit_id:(.commit_id // null),commit_url:(.commit_url // null)}'

Length of output: 2563


@raphaeltm The repository configuration did not suppress the review.

auto_review.enabled is true. This PR has no excluded label, base branch, title keyword, path, or configured username. It was also not a draft.

The relevant difference is the PR author. GitHub reports simple-agent-manager[bot] as the author. This is a GitHub App bot account. Bot-authored PRs can be skipped by automatic review safeguards to prevent automation loops.

GitHub shows no CodeRabbit check run, review, or comment on #1846. Therefore, CodeRabbit did not start an automatic review job.

I cannot distinguish, from the available GitHub data alone, between the bot-author safeguard and an internal event-delivery or processing failure. The bot author is the likely cause.

You can request a review explicitly with @coderabbitai review on the PR.

You are interacting with an AI system.

@raphaeltm

Copy link
Copy Markdown
Owner

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain
🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="raphaeltm/simple-agent-manager"
pr_number="1846"

echo '=== PR metadata ==='
gh pr view "$pr_number" --repo "$repo" \
  --json number,state,isDraft,createdAt,updatedAt,author,baseRefName,headRefName,labels,reviewRequests,statusCheckRollup \
  --jq '{number,state,isDraft,createdAt,updatedAt,author:.author.login,baseRefName,headRefName,labels:[.labels[].name],reviewRequests:[.reviewRequests[].login],checks:[.statusCheckRollup[]? | {name:.name,conclusion:.conclusion,status:.status}]}'

echo '=== Recent PR timeline events ==='
gh api "repos/$repo/issues/$pr_number/timeline" \
  -H 'Accept: application/vnd.github+json' \
  --paginate \
  --jq '.[] | select(.event == "labeled" or .event == "unlabeled" or .event == "ready_for_review" or .event == "converted_to_draft" or .event == "review_requested" or .event == "head_ref_force_pushed" or .event == "committed" or .event == "closed" or .event == "reopened") | {event,created_at,actor:(.actor.login // null),label:(.label.name // null),commit_id:(.commit_id // null)}'

Length of output: 3679

⚙️ CodeRabbit configuration inspected

Length of output: 5450

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="raphaeltm/simple-agent-manager"
pr_number="1846"
head_sha=$(gh pr view "$pr_number" --repo "$repo" --json headRefOid --jq '.headRefOid')

echo '=== Pull request state and author ==='
gh api "repos/$repo/pulls/$pr_number" \
  --jq '{number,created_at,updated_at,draft,user:{login:.user.login,type:.user.type},author_association}'

echo '=== Pull request reviews ==='
gh api "repos/$repo/pulls/$pr_number/reviews" --paginate \
  --jq '.[] | {submitted_at,state,user:(.user.login // null),body}'

echo '=== Pull request issue comments with CodeRabbit mentions ==='
gh api "repos/$repo/issues/$pr_number/comments" --paginate \
  --jq '.[] | select((.user.login | ascii_downcase | contains("coderabbit")) or (.body | ascii_downcase | contains("coderabbit"))) | {created_at,user:.user.login,body}'

echo '=== Check runs from CodeRabbit ==='
gh api "repos/$repo/commits/$head_sha/check-runs" \
  -H 'Accept: application/vnd.github+json' --paginate \
  --jq '.check_runs[] | select((.app.slug // "" | ascii_downcase | contains("coderabbit")) or (.name | ascii_downcase | contains("coderabbit"))) | {name,status,conclusion,started_at,completed_at,app:(.app.slug // null),details_url}'

echo '=== Pull request timeline: state-changing events ==='
gh api "repos/$repo/issues/$pr_number/timeline" \
  -H 'Accept: application/vnd.github+json' --paginate \
  --jq '.[] | select(.event == "opened" or .event == "ready_for_review" or .event == "converted_to_draft" or .event == "synchronize" or .event == "review_requested" or .event == "committed") | {event,created_at,actor:(.actor.login // null),commit_id:(.commit_id // null),commit_url:(.commit_url // null)}'

Length of output: 2563

@raphaeltm The repository configuration did not suppress the review.

auto_review.enabled is true. This PR has no excluded label, base branch, title keyword, path, or configured username. It was also not a draft.

The relevant difference is the PR author. GitHub reports simple-agent-manager[bot] as the author. This is a GitHub App bot account. Bot-authored PRs can be skipped by automatic review safeguards to prevent automation loops.

GitHub shows no CodeRabbit check run, review, or comment on #1846. Therefore, CodeRabbit did not start an automatic review job.

I cannot distinguish, from the available GitHub data alone, between the bot-author safeguard and an internal event-delivery or processing failure. The bot author is the likely cause.

You can request a review explicitly with @coderabbitai review on the PR.

You are interacting with an AI system.

@coderabbitai is there any way for me to explicitly ask that PRs from that bot get reviewed? I do all my work through that bot.

@coderabbitai

coderabbitai Bot commented Aug 27, 2026

Copy link
Copy Markdown

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

⚙️ CodeRabbit configuration inspected

Length of output: 5450


@raphaeltm Yes. For an individual pull request, add this top-level PR comment:

`@coderabbitai` review

That explicitly requests a review. You can have simple-agent-manager[bot] post that comment when it opens the PR, if its GitHub App permissions allow issue comments.

The current configuration has no setting to allow-list bot authors. reviews.auto_review.ignore_usernames only excludes authors. It cannot opt in simple-agent-manager[bot].

Therefore, there is no repository YAML change that I can recommend to restore automatic review for every PR from that bot. For a permanent automatic solution, contact CodeRabbit support and request a bot-author exception for:

simple-agent-manager[bot]

For now, use @coderabbitai review on each PR.

You are interacting with an AI system.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant