From be35efc6d05ee51d209035bb227f5cfac6beeb61 Mon Sep 17 00:00:00 2001
From: Mark IJbema <mark@kilocode.ai>
Date: Mon, 23 Feb 2026 10:25:56 +0100
Subject: [PATCH 1/2] Improve stale workflow: close old issues/PRs with
 friendlier messages

---
 .github/workflows/stale-issues.yml | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/.github/workflows/stale-issues.yml b/.github/workflows/stale-issues.yml
index 2dc74b62fd5..f191abb9c2c 100644
--- a/.github/workflows/stale-issues.yml
+++ b/.github/workflows/stale-issues.yml
@@ -6,28 +6,29 @@ on:
   workflow_dispatch:
 
 env:
-  DAYS_BEFORE_STALE: 90
-  DAYS_BEFORE_CLOSE: 7
+  DAYS_BEFORE_ISSUE_CLOSE: 90
+  DAYS_BEFORE_PR_CLOSE: 30
 
 jobs:
   stale:
     runs-on: blacksmith-4vcpu-ubuntu-2404
     permissions:
       issues: write
+      pull-requests: write
     steps:
       - uses: actions/stale@v10
         with:
-          days-before-stale: ${{ env.DAYS_BEFORE_STALE }}
-          days-before-close: ${{ env.DAYS_BEFORE_CLOSE }}
-          stale-issue-label: "stale"
+          days-before-issue-stale: ${{ env.DAYS_BEFORE_ISSUE_CLOSE }}
+          days-before-pr-stale: ${{ env.DAYS_BEFORE_PR_CLOSE }}
+          days-before-issue-close: 0
+          days-before-pr-close: 0
           close-issue-message: |
-            [automated] Closing due to ${{ env.DAYS_BEFORE_STALE }}+ days of inactivity.
+            Closing this one out since it's been inactive for a while — not because it's a bad issue, just that older items tend to lose context over time and we'd rather start fresh if this is still a problem.
 
-            Feel free to reopen if you still need this!
-          stale-issue-message: |
-            [automated] This issue has had no activity for ${{ env.DAYS_BEFORE_STALE }} days.
+            Please feel free to reopen (or open a new issue) if you're still running into this. We're happy to take another look! 🙏
+          close-pr-message: |
+            Closing this one out since it's been inactive for a while — not because it's a bad PR, just that older items tend to lose context over time and we'd rather start fresh if this is still relevant.
 
-            It will be closed in ${{ env.DAYS_BEFORE_CLOSE }} days if there's no new activity.
-          remove-stale-when-updated: true
+            Please feel free to reopen (or open a new PR) if you're still working on this. We're happy to take another look! 🙏
           exempt-issue-labels: "pinned,security,feature-request,on-hold"
-          start-date: "2025-12-27"
+          exempt-pr-labels: "pinned,security,on-hold"

From e30a50353276481b0c7785a48d9113975b5f533a Mon Sep 17 00:00:00 2001
From: Mark IJbema <mark@kilocode.ai>
Date: Mon, 23 Feb 2026 10:39:28 +0100
Subject: [PATCH 2/2] docs: add issue and PR lifecycle policy to
 CONTRIBUTING.md

---
 .github/workflows/stale-issues.yml | 2 --
 CONTRIBUTING.md                    | 4 ++++
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/stale-issues.yml b/.github/workflows/stale-issues.yml
index f191abb9c2c..876e0fc02c9 100644
--- a/.github/workflows/stale-issues.yml
+++ b/.github/workflows/stale-issues.yml
@@ -30,5 +30,3 @@ jobs:
             Closing this one out since it's been inactive for a while — not because it's a bad PR, just that older items tend to lose context over time and we'd rather start fresh if this is still relevant.
 
             Please feel free to reopen (or open a new PR) if you're still working on this. We're happy to take another look! 🙏
-          exempt-issue-labels: "pinned,security,feature-request,on-hold"
-          exempt-pr-labels: "pinned,security,on-hold"
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 65884d6d248..b122ccdf82f 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -77,6 +77,10 @@ kilo web             # Start server + open web interface
 - **Logic Changes:** Explain how you verified it works.
 - **PR Titles:** Follow conventional commit standards (`feat:`, `fix:`, `docs:`, etc.).
 
+### Issue and PR Lifecycle
+
+To keep our backlog manageable, we automatically close inactive issues and PRs after a period of inactivity. This isn't a judgment on quality — older items tend to lose context over time and we'd rather start fresh if they're still relevant. Feel free to reopen or create a new issue/PR if you're still working on something!
+
 ### Style Preferences
 
 - **Functions:** Keep logic within a single function unless breaking it out adds clear reuse.