Skip to main content

Kuroco roadmap

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

2026

Jul. Next 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.

External Integration

  • You will be able to filter the branches displayed in the GitHub workflow execution list for KurocoFront, allowing you to show only branches that are relevant to your integration.

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.
  • A pre-copy UI similar to the one used for primary-language copy will be shown when copying content in a secondary language. This allows duplicate slug errors to be displayed in the correct UI (instead of an empty edit screen) and lets you adjust the primary-language content before performing the copy.
  • In the content list view, link-type extension field columns will be displayed as clickable hyperlinks (<a> tags that open in a new tab) instead of raw JSON strings.
  • When specifying an endpoint URL in an API field item using a relative path, ROOT_API_URL will be automatically prepended.

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.

Specification Changes

  • When uploading member CSV files, if the Enable group settings in the CSV setting was enabled, members were previously updated with no group assigned when the CSV used for the update did not include a group column. This behavior has been changed so that if the CSV used for the update does not have a group column, the group update will be ignored.

Oct. Later releases

The schedule for Later Releases will be announced when the details are finalized.


Support

If you have any other questions, please contact us or check out Our Slack Community.