Kuroco roadmap

Currently, we are focusing on improving the UI/UX of Kuroco's admin panel and developing external integrations.

2026

Apr. Next releases
(Apr 22, 10:00 AM - 1:00 PM)

New Features

AI

• Kuroco Skills for Claude Code is now available. A skill package that enables Claude Code to directly operate Kuroco via the Management API, including content management, API configuration, batch processing, and deployment automation.
• A setting for [AI post-processing after content updates] is now available. You can automatically run AI-powered processing such as translation when content is created or updated.
• Admin CLI (kuroco-admin) and Client CLI (kuroco-client) are now available. CLI tools for interacting with Kuroco APIs from the terminal, designed for automation and AI agent integration.

API

• The Management API (admin_api) is now available. You can perform admin panel operations via API, including content creation, member management, and API configuration.
• [llms.txt for the management screen] is now available. You can retrieve API documentation in a format optimized for AI assistants.
• [Email API] is now available, allowing you to send emails via API endpoints.
• [LINE API] is now available, enabling LINE message sending via API endpoints.
• [Slack API] is now available, enabling Slack message sending via API endpoints.
• A langs_open_flg parameter has been added to the Topics::list and Topics::details endpoints. When enabled, each topic includes a langs_open_flg object showing publication status for all configured languages (e.g. {“en”:1,”ja”:0}), enabling multi-language sites to display language switchers without making separate API requests per language.
• The Topics::waiting_for_approval_details endpoint will support specifying multiple topics_group_id values.
• The Topics::draft_list endpoint will support specifying multiple topics_group_id values.
• An endpoint for Files::temp_upload_url will be added.
• A schema parameter will be added to the OpenAI::chat endpoint. By specifying a JSON Schema, you can obtain AI output in a structured JSON format.

External Integration

• A "CORS auto-update" setting has been added to the Amazon S3 settings screen. When disabled, Kuroco stops automatically updating the S3 CORS configuration, allowing you to manage CORS settings directly on the AWS side.

Content Management

• A “Download as ZIP” feature has been added to the file manager. When 2 or more files are selected, you can download them as a single ZIP archive. The total download size is limited to 500MB.

Form

• If “Also include time (hh:mm)” is enabled in the date format settings, the hh:mm information will also be assigned to the message template.

Tag

• When downloading the tag list as a CSV, the tags will be exported in the order they are displayed.

Content

• An "Allow all tags" option will be added to the WYSIWYG input restriction settings. When enabled, all tags including <script> and <iframe> tags will be available.
• A new constant USE_SAFE_SVG_TAGS will be added, allowing safe SVG tags to be used in HTML and WYSIWYG fields.
• A Strikethrough (line-through) button has been added to the CKEditor 5 toolbar. By setting strikethrough::1 in wysiwyg_options of the content structure, the strikethrough button will appear in the toolbar after the underline button.
• You will be able to select the return destination when rejecting in an approval workflow.
• Applicants will be able to withdraw an approval workflow request.
• Custom member filters will be able to be used for approval groups in approval workflows.

Custom Function

• Modules can now be configured to set "All modules" as trigger targets for content triggers.

Specification Changes

• When the check_current_pwd parameter is enabled in Member::update, the system will also validate current_password when changing the email address.
• When the check_current_pwd parameter is enabled on the Member::update endpoint, the error key related to current_password was incorrectly set to login_pwd. This will be corrected to current_password.
• Free users (users who have not registered payment information) will be subject to restrictions on batch processing (approximately 100 executions per hour) and API sending (approximately 1,000 requests per hour).
  info

  Information -> Limiting Batch Processing and API Sending for Free Users

• When specifying the "Approval date and time" and content is updated by a batch process, the updater will be recorded as the member who performed the approval, rather than Member ID = 1.
• For email two-factor authentication, if Email/SMS cannot be sent due to a backend issue, login will now fail by default. To maintain the previous behavior (allowing login without the authentication code), set the constant REJECT_MFA_LOGIN_IF_SEND_FAILED to 0.
  info

  Information -> Change in Email Two-Factor Authentication Behavior When Email Cannot Be Sent

Jul. Later releases

New Features

Security

• Backup codes will be added for Two-Factor Authentication (TFA). Backup codes will be generated when TFA is set up, allowing account access even if the authentication device is lost.

Content

• The "Visibility of content in Admin panel" trigger will now also apply to pending approval content and saved draft content. This allows including pending approval content when restricting display and editing to content created by members of the same group.
• The UI for Boolean type extension fields will be updated.
• Sorting by extension columns in the content list will be available.

API

• Filtering by category slug will be available in TopicsCategory::list.
• A TopicsGroup::update API endpoint will be added.
• An apply_member_id parameter will be added to Approvalflow::list.
• An unuse_columns setting will be added to Topics::bulk_download, allowing unnecessary columns to be excluded from downloads.