You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replace prefix-based feature request detection with Claude-driven intent detection
Chat system prompt now instructs Claude to append [FEATURE] or [IMPROVEMENT]
markers when it detects a feature request intent. The marker is stripped before
display/history and routes to the cog's new start_from_intent() method. No
extra API call — piggybacks on the existing chat call. Explicit prefixes
("feature request:", "bot improvement:") still work as before.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
-**Chat**: @mention the bot → Claude responds with per-channel conversation memory (last 20 messages)
51
-
-**Feature requests**: @mention with "feature request: <description>" → role check → creates Discord thread → multi-turn planning conversation with Claude → user confirms → code gen → AST scan → opens PR
52
-
-**Bot improvements**: @mention with "bot improvement: <description>" → role check → creates Discord thread → planning conversation → user confirms → code gen → PR flagged as CORE CHANGE
51
+
-**Intent detection**: During chat, the system prompt instructs Claude to append `[FEATURE]` or `[IMPROVEMENT]` markers when it detects the user wants a feature. The marker is stripped before display/history and routes to the feature request flow. No extra API call — piggybacks on the existing chat call.
52
+
-**Feature requests**: Detected naturally via chat intent, or explicitly with "feature request: <description>" → role check → creates Discord thread → multi-turn planning conversation with Claude → user confirms → code gen → AST scan → opens PR
53
+
-**Bot improvements**: Detected naturally via chat intent, or explicitly with "bot improvement: <description>" → role check → creates Discord thread → planning conversation → user confirms → code gen → PR flagged as CORE CHANGE
Copy file name to clipboardExpand all lines: PRIVACY_POLICY.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ When you @mention the Bot, the text of your message (with the mention stripped)
17
17
18
18
### 1.2 Feature Request Content
19
19
20
-
When you submit a feature request or bot improvement, the Bot creates a **Discord thread** for a collaborative planning conversation. During this process:
20
+
The Bot detects feature request intent during normal chat — no additional API call is made for intent detection. When a feature request is identified (either through natural language detection or an explicit prefix), the Bot creates a **Discord thread** for a collaborative planning conversation. During this process:
21
21
22
22
- Your request description and all follow-up messages in the thread are sent to the Anthropic Claude API for planning and code generation
23
23
- The conversation history for the thread is stored in application memory (RAM) for the duration of the session (up to 30 minutes of inactivity) and is lost on Bot restart
Copy file name to clipboardExpand all lines: README.md
+19-5Lines changed: 19 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,24 +67,38 @@ The supervisor manages the bot lifecycle, handles deploys on PR merge, and rolls
67
67
68
68
### Feature Requests (Plugin)
69
69
70
+
Just describe what you want in natural language:
71
+
70
72
```
71
-
@Turbot feature request: add a command that tells jokes
73
+
@Turbot can you add a command that tells jokes?
72
74
```
73
75
74
-
The bot creates a **Discord thread** and starts a collaborative planning conversation. It will ask clarifying questions, propose an implementation plan, and wait for your confirmation before generating code. Once you reply **go**, it generates a sandboxed plugin in `plugins/`, scans it for security policy violations, and opens a PR. Reply **cancel** to abort at any time. Requires the `BotAdmin` role (configurable).
76
+
Turbot detects the intent automatically during normal chat. When it recognizes a feature request, it creates a **Discord thread** and starts a collaborative planning conversation. It will ask clarifying questions, propose an implementation plan, and wait for your confirmation before generating code. Once you reply **go**, it generates a sandboxed plugin in `plugins/`, scans it for security policy violations, and opens a PR. Reply **cancel** to abort at any time. Requires the `BotAdmin` role (configurable).
77
+
78
+
You can also use the explicit prefix if you prefer:
79
+
```
80
+
@Turbot feature request: add a command that tells jokes
81
+
```
75
82
76
83
### Bot Improvements (Core)
77
84
85
+
If Turbot detects you want to change its core behavior, it routes through the improvement flow:
86
+
78
87
```
79
-
@Turbot bot improvement: add rate limiting to chat responses
88
+
@Turbot can you make the error messages friendlier?
80
89
```
81
90
82
91
Same conversational flow as feature requests, but this can modify any file in the project. The PR is flagged with "CORE CHANGE" and triggers an admin channel warning.
83
92
93
+
Explicit prefix also works:
94
+
```
95
+
@Turbot bot improvement: add rate limiting to chat responses
96
+
```
97
+
84
98
### Feature Request Flow
85
99
86
-
1. User submits a request in any channel
87
-
2. Bot creates a thread and evaluates the request
100
+
1. User @mentions the bot with a request (natural language or explicit prefix)
Copy file name to clipboardExpand all lines: TERMS_OF_SERVICE.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ You agree not to:
24
24
25
25
## 4. Feature Requests and Generated Code
26
26
27
-
- Feature requests and bot improvements are handled through a **conversational planning process** in Discord threads. The Bot will ask clarifying questions and propose a plan before generating code
27
+
- Feature requests and bot improvements can be triggered through natural language or explicit prefixes, and are handled through a **conversational planning process** in Discord threads. The Bot will ask clarifying questions and propose a plan before generating code
28
28
- You may confirm the plan to proceed with code generation, or cancel the request at any time
29
29
- Feature request sessions time out after 30 minutes of inactivity
30
30
- All generated code is subject to review before merge; the Bot does not auto-apply changes
0 commit comments