Skip to content
DevAgentRadarDevAgentRadar
Sign in
Proposals/Enable KIROCREW_CREW_LOG and GitLab/Bitbucket/Az
proposaleveryoneP3Worth a lookKiro

Enable KIROCREW_CREW_LOG and GitLab/Bitbucket/Azure DevOps PR watches

Kiro Crew 0.7 applies most settings live, keeps accepted background work across Gateway restarts, and adds GitLab, Bitbucket Cloud, and Azure DevOps PR watches. Enable the Crew log, multi-forge watches, Steer/Queue, and optional Jev routing so long-running agent work is recoverable and controllable.

Why this loop

Kiro Crew 0.7.0 (this 0.7.2 signal) makes agent work survive Gateway restarts: accepted subagent work, Task Runner steps, and workflow calls enqueue durably, and the System page shows the queue and concurrency capacity. Set KIROCREW_CREW_LOG=1 in ~/.kiro/crew/.env and restart the Gateway for an append-only Crew log and session ledger across compaction (kirocrew-crew-log MCP is read-only). Most config.json and Settings changes apply live; the Slack slash-command field still needs a restart. Chat now has a turn minimap, a combined model/reasoning chip (Selectable Models), Steer vs Queue (Cmd/Ctrl+Enter flips the other), and Side Chat via /side or /btw. PR watches accept GitHub, GitLab (glab), Bitbucket Cloud (BITBUCKET_EMAIL, BITBUCKET_API_TOKEN), and Azure DevOps Services (az + azure-devops, az login or AZURE_DEVOPS_EXT_PAT); not Azure DevOps Server or Bitbucket Data Center; Azure DevOps and private Bitbucket watches must start from a dashboard conversation. Preview: OpenCode/goose backends, Pi without Crew MCP tools, and Auto (Jev) after enabling Decisions (Jev).

Proposed actions

  1. printf '\nKIROCREW_CREW_LOG=1\n' >> ~/.kiro/crew/.env && echo 'Restart the Kiro Gateway, then open System to confirm the durable queue, concurrency capacity, and Crew log status/usage/timeline/tools/approvals views. Agents can read the log via the kirocrew-crew-log MCP server.'
  2. Install and authenticate the forge CLI for each PR host you watch: GitLab → glab; Azure DevOps Services → az extension add --name azure-devops plus az login or AZURE_DEVOPS_EXT_PAT; private Bitbucket Cloud → BITBUCKET_EMAIL and BITBUCKET_API_TOKEN. Start Azure DevOps and private Bitbucket watches from a dashboard conversation. Do not target Azure DevOps Server or Bitbucket Data Center.
  3. In desktop chat, use the left-gutter turn minimap (hover preview, click-to-jump, end cap loads older history). Set model and reasoning effort on the model chip via Selectable Models. While the agent is working, choose Steer to redirect the current turn or Queue for the next; Cmd/Ctrl+Enter sends the other action.
  4. Enable Decisions (Jev) under Settings > Developer > Feature Previews, then select Auto (Jev) in the chat model picker and on the busy send button so each message is classified simple/medium/complex via decisions.model_route and mid-turn messages steer or queue. Review the per-message decision chip and the consent switches for tool arguments, compaction inputs, and recalled-memory snippets.
  5. Type /side or /btw to open Side Chat for an ephemeral question (Kiro CLI backend: read-only lookups without approval; changes and MCP tools refused). In Preview, add OpenCode or goose in the Agent Backend selector after Crew verifies the permission path; skip Pi when you need Crew subagents, scheduling, memory, or other MCP tools (kirocrew doctor reports this). Copy tables as Markdown or CSV.

Agent prompt

Paste into your agent or query via MCP (get_agent_prompt) — free, no extra AI cost

Copilot Chat / Agent mode

DevAgentRadar → GitHub Copilot

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

Context

Assistant: Kiro Proposal: Enable KIROCREW_CREW_LOG and GitLab/Bitbucket/Azure DevOps PR watches Summary: Kiro Crew 0.7 applies most settings live, keeps accepted background work across Gateway restarts, and adds GitLab, Bitbucket Cloud, and Azure DevOps PR watches. Enable the Crew log, multi-forge watches, Steer/Queue, and optional Jev routing so long-running agent work is recoverable and controllable. Primary source: https://kiro.dev/changelog/crew/0-7#patch-0-7-2

Why it matters

Kiro Crew 0.7.0 (this 0.7.2 signal) makes agent work survive Gateway restarts: accepted subagent work, Task Runner steps, and workflow calls enqueue durably, and the System page shows the queue and concurrency capacity. Set KIROCREW_CREW_LOG=1 in ~/.kiro/crew/.env and restart the Gateway for an append-only Crew log and session ledger across compaction (kirocrew-crew-log MCP is read-only). Most config.json and Settings changes apply live; the Slack slash-command field still needs a restart. Chat now has a turn minimap, a combined model/reasoning chip (Selectable Models), Steer vs Queue (Cmd/Ctrl+Enter flips the other), and Side Chat via /side or /btw. PR watches accept GitHub, GitLab (glab), Bitbucket Cloud (BITBUCKET_EMAIL, BITBUCKET_API_TOKEN), and Azure DevOps Services (az + azure-devops, az login or AZURE_DEVOPS_EXT_PAT); not Azure DevOps Server or Bitbucket Data Center; Azure DevOps and private Bitbucket watches must start from a dashboard conversation. Preview: OpenCode/goose backends, Pi without Crew MCP tools, and Auto (Jev) after enabling Decisions (Jev).

Suggested actions

  1. printf '\nKIROCREW_CREW_LOG=1\n' >> ~/.kiro/crew/.env && echo 'Restart the Kiro Gateway, then open System to confirm the durable queue, concurrency capacity, and Crew log status/usage/timeline/tools/approvals views. Agents can read the log via the kirocrew-crew-log MCP server.'
  2. Install and authenticate the forge CLI for each PR host you watch: GitLab → glab; Azure DevOps Services → az extension add --name azure-devops plus az login or AZURE_DEVOPS_EXT_PAT; private Bitbucket Cloud → BITBUCKET_EMAIL and BITBUCKET_API_TOKEN. Start Azure DevOps and private Bitbucket watches from a dashboard conversation. Do not target Azure DevOps Server or Bitbucket Data Center.
  3. In desktop chat, use the left-gutter turn minimap (hover preview, click-to-jump, end cap loads older history). Set model and reasoning effort on the model chip via Selectable Models. While the agent is working, choose Steer to redirect the current turn or Queue for the next; Cmd/Ctrl+Enter sends the other action.
  4. Enable Decisions (Jev) under Settings > Developer > Feature Previews, then select Auto (Jev) in the chat model picker and on the busy send button so each message is classified simple/medium/complex via decisions.model_route and mid-turn messages steer or queue. Review the per-message decision chip and the consent switches for tool arguments, compaction inputs, and recalled-memory snippets.
  5. Type /side or /btw to open Side Chat for an ephemeral question (Kiro CLI backend: read-only lookups without approval; changes and MCP tools refused). In Preview, add OpenCode or goose in the Agent Backend selector after Crew verifies the permission path; skip Pi when you need Crew subagents, scheduling, memory, or other MCP tools (kirocrew doctor reports this). Copy tables as Markdown or CSV.

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/kiro-0-7-2-enable-kirocrew-crew-log-and-gitlab-bitbucket-azure-devops-pr and mark Applied, Skipped, or Failed. Proposal id: 669a5865-0110-405b-995f-83448738194c

Your job

  1. Restate the change in one sentence.
  2. Propose a minimal plan for my repo (or a throwaway pilot).
  3. Implement only what I approve; prefer small diffs and tests.
  4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.

Release source ↗

Your loop

This browser · no sign-in · not shared as “you”

After you run the prompt

Only you can mark this. Agents cannot write your loop.

Your decision stays on this device. A public tally appears after a few votes.

Originating release signal

Kiro0.7.2Sep 28, 2026

Sep 28, 2026

September 24, 2026 Live Settings, Durable Work, and Broader Pull Request Watches · 0.7.0 · Kiro Crew 0.7.0 makes day-to-day work more durable and easier to control. · Most settings apply as soon as you save them, accepted background work survives Gateway restarts, and updates wait for active work to finish. · Long chats gain a turn minimap, clearer tool-call titles, and direct model and reasoning controls, while pull request watches expand to GitLab, Bitbucket Cloud, and Azure DevOps Services. · +45 more changes
Verified excerpt — the source's own words

September 24, 2026 Live Settings, Durable Work, and Broader Pull Request Watches 0.7.0 Kiro Crew 0.7.0 makes day-to-day work more durable and easier to control. Most settings apply as soon as you save them, accepted background work survives Gateway restarts, and updates wait for active work to finish. Long chats gain a turn minimap, clearer tool-call titles, and direct model and reasoning controls, while pull request watches expand to GitLab, Bitbucket Cloud, and Azure DevOps Services. Windows gets isolated pods and a faster Gateway start, and Preview users can choose more agent backends, let Jev route individual turns, or run remote crews on AWS Fargate. Settings That Apply While You Work Most settings now reach the running Gateway as soon as you save config.json or change a value in Settings. Fields that still need a restart identify themselves in the UI; the Slack slash-command field is the current boot-only setting and carries a Changes need a restart badge. Learn more -> Chat That Keeps Up With You

Excerpt ends here — this release continues at the source ↗.

Primary source ↗