towns-agent 7.1.0 → 7.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -83,7 +83,7 @@ Requires `APP_PRIVATE_KEY` (or `APP_PRIVATE_DATA`) to be set in `.env` or the en
83
83
 
84
84
  ### `setup [appAddress]`
85
85
 
86
- Register a webhook URL and configure notification settings for an app.
86
+ Register a webhook URL, configure notification settings, and declare supported APIs for an app.
87
87
 
88
88
  The `appAddress` argument is optional when running inside a project that has a `.env` file containing `APP_ADDRESS` or `APP_PRIVATE_DATA`.
89
89
 
@@ -99,6 +99,12 @@ bun run cli setup \
99
99
  --ownerPrivateKey 0xac09... \
100
100
  --webhookUrl https://example.com/webhook \
101
101
  --notify ALL
102
+
103
+ # Enable the positions API
104
+ bun run cli setup \
105
+ --ownerPrivateKey 0xac09... \
106
+ --webhookUrl https://example.com/webhook \
107
+ --features positions
102
108
  ```
103
109
 
104
110
  Options:
@@ -110,10 +116,12 @@ Options:
110
116
  - `ALL` — Forward all messages
111
117
  - `MENTION_REPLY_REACTION` — Forward mentions, replies, and reactions only
112
118
  - `NONE` — Forward no messages
119
+ - `-f, --features <list>` — Comma-separated list of supported APIs to declare. Available features:
120
+ - `positions` — App supports the positions API (returns `PositionsResponse` via `GetAppPositions`)
113
121
 
114
122
  ### `setup view [appAddress]`
115
123
 
116
- View the current webhook URL and notification settings for an app.
124
+ View the current webhook URL, notification settings, and supported APIs for an app.
117
125
 
118
126
  ```bash
119
127
  # From a project with .env
@@ -164,15 +172,13 @@ Options:
164
172
 
165
173
  ### `admin [appAddress]`
166
174
 
167
- Admin workflow for app status and metadata updates.
175
+ Admin workflow for app metadata updates.
168
176
 
169
177
  The command:
170
178
 
171
179
  1. Authenticates (supports bearer token, same as other commands)
172
- 2. Shows current promoted status, verified status, and metadata
173
- 3. Calls `SetAppPromotedStatus`
174
- 4. Calls `SetAppVerifiedStatus`
175
- 5. Calls `UpdateAppMetadata` using either a guided editor or a pasted patch
180
+ 2. Shows current metadata
181
+ 3. Calls `UpdateAppMetadata` using either a guided editor or a pasted patch
176
182
 
177
183
  The `appAddress` argument is optional when running inside a project that has a `.env` file containing `APP_ADDRESS` or `APP_PRIVATE_DATA`. If it is not found, the CLI prompts for it so you can paste the address.
178
184