admin/cyclop
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs: Correct roadmap-issue alignment in README.md

Browse Source
This commit is contained in:
cyclop-bot
2025-06-02 16:24:20 -05:00
parent dd279e64e3
commit 3772b79d7d
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -4
View File
@@ -109,11 +109,11 @@ Here are some of the upcoming features and improvements planned for the bot:
* Reviewing Pull Requests. * Reviewing Pull Requests.
* Analyzing metrics. * Analyzing metrics.
(Issue #196) (Issue #196)
*Note: For timed agent tasks, API keys and other sensitive information will be stored server-side, envisioning a future paid service model.* * **Enhanced onboarding and GitHub configuration:**
* **Enhanced onboarding and configuration:**
* On `/start`, prompt the user for a GitHub API key and provide a pre-configured link to generate a new key with the required permissions. * On `/start`, prompt the user for a GitHub API key and provide a pre-configured link to generate a new key with the required permissions.
* Validate the API key and then ask for the target repository. * Validate the API key and then ask for the target repository.
* Store the GitHub API key and current repository in `context.user_data["github_api_key"]` and `context.user_data["current_repository"]` respectively on the Telegram side.
(Issue #197) (Issue #197)
* **Repository switching command:** Implement a command to allow users to switch between different GitHub repositories seamlessly. (Issue #198) * **Repository switching command:** Implement a command to allow users to switch between different GitHub repositories seamlessly. (Issue #198)
* **User data storage for GitHub:** Store the GitHub API key and current repository in `context.user_data["github_api_key"]` and `context.user_data["current_repository"]` respectively on the Telegram side. (Issue #199) * **User-provided inference service API keys:** Allow users to input their own API keys for inference services (e.g., OpenAI, Gemini, Anthropic, other OpenAI-compatible services). These keys will be stored in `context.user_data`. A wizard may be implemented to guide users through obtaining API keys if needed. (Issue #199)
* **User-provided inference service API keys:** Allow users to input their own API keys for inference services (e.g., OpenAI, Gemini, Anthropic, other OpenAI-compatible services). These keys will be stored in `context.user_data`. A wizard may be implemented to guide users through obtaining API keys if needed. (Issue #200) * **Server-side storage for timed agents:** For agents running on a timer, API keys and other sensitive information will be stored server-side. This will eventually be a paid service. (Issue #200)