Home / Guides / Poolside Laguna S 2.1

Updated July 22, 2026 · applies to pgup-ai/jbot-review-action v0

Laguna S 2.1 can review pull requests through Poolside's first-party API, free during its limited-time preview. J-Bot Review now has a direct poolside backend—no CLI or generic compatibility adapter required. The same model also has free OpenCode and OpenRouter routes.

Direct Poolside setup in three steps

1. Create a Poolside API key. Start from Poolside's Laguna page, then save the key as the repository secret POOLSIDE_API_KEY (Settings → Secrets and variables → Actions).
2. Commit the workflow. Add the file below as .github/workflows/jbot-review.yml. Laguna S 2.1 is already the backend default; the explicit model pin keeps the configuration readable.
3. Open a pull request. J-Bot reads the base…head diff and posts diff-anchored findings with a verdict. Blocking findings are checked by a second session before they post.

name: J-Bot Code Review
on:
  pull_request: { types: [opened, reopened, ready_for_review, synchronize] }

concurrency:
  group: jbot-review-${{ github.event.pull_request.number }}
  cancel-in-progress: true

permissions:
  contents: read
  pull-requests: write
  issues: write
  checks: read

jobs:
  review:
    if: github.event.pull_request.draft == false
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
        with: { fetch-depth: 0 }
      - uses: pgup-ai/jbot-review-action@v0
        with:
          provider: poolside
          model: poolside/laguna-s-2.1
          poolside-api-key: ${{ secrets.POOLSIDE_API_KEY }}
          github-token: ${{ secrets.GITHUB_TOKEN }}

Three free routes, three model ids

Laguna S 2.1 is free through all three routes today. Pick based on where you already manage keys; free windows, quotas, and context limits remain provider-controlled.

Why Laguna S 2.1 fits review work

• It is built for long-horizon coding. Poolside describes S 2.1 as a 118B-parameter mixture-of-experts model with 8B active parameters and up to a 1M-token context window.
• It emphasizes persistence and verification. The launch report focuses on longer sessions, tool use, backtracking, and finishing work instead of declaring victory early—the same behaviors a useful reviewer needs.
• The model is open-weight. Poolside released the weights on launch day; the hosted routes above are the convenient CI path, while self-hosting remains possible outside this guide.
• J-Bot adds $0. The Action is MIT-licensed, with no reviewer service and no per-seat fee. During the free preview, your remaining cost is normal GitHub Actions minutes.

Where the diff goes

• Your runner stays in control. The review session runs headless on your GitHub Actions runner with read-only repository access.
• Direct means direct. With provider: poolside, the diff goes to Poolside's API on your own key. There is no J-Bot server or generic OpenCode gateway in that path.
• Fork PRs cannot read the key. GitHub does not pass repository secrets to pull_request workflows from forks.
• Blocking findings are verified. A second model session challenges each blocking finding before J-Bot posts it; nits are demoted.

FAQ

Related