Crux – AI agents built into Redmineflux. Ask. Approve. Done.
Ask Crux knows your projects. Crux agents pick up real work and propose changes – nothing is written until a person confirms it.
Crux is the AI layer of Redmineflux. It adds Ask Crux, a chat that answers from your Redmine data, and 26 ready-made agents that propose changes – nothing is written until a person approves it. Crux needs the Redmineflux MCP Server. $699 one-time for self-hosted Redmine; included in every Cloud package. AI for Redmine overview →
Ask about projects, issues and what the agents are doing. Crux looks the answer up in Redmine before it replies.
Specialists such as Project Manager, Sales, Support and Time that pick up real work and propose changes. Nothing is applied until a person approves it.
- Progress: 58 issues, 18% complete – 24 new, 7 in progress, 7 resolved
- Milestones: R1–R3 active; R3 due 25 Sep, 13 days overdue
- Risk: #450337 flagged Immediate, awaiting feedback
Crux wants to make this change. Nothing happens until you confirm.
AI can write a plan, but it cannot touch the project – or it touches too much.
Generic assistants don’t know your issues, your versions or who is busy. Give one write access and nobody can say afterwards what it changed, what it cost, or who said yes. So the useful work still happens by hand.
People stay in control at every step.
In chat, every change Crux proposes is shown to you first and runs only after you confirm it. Larger pieces of work follow pipelines with approval gates, and work cannot move past a gate until a person approves it.
Every run is logged in the Run Ledger with its time, tokens, cost and result – a full, auditable history.
What is Crux?
Crux is the AI layer of Redmineflux. It adds two things to your Redmine workspace: Ask Crux, a chat assistant that already knows your projects, issues and agent activity, and Crux agents – specialists that can pick up real work and propose changes.
Crux lives inside Redmineflux. It uses the same pages, permissions and look as the rest of the suite. There is no separate tool to learn.
Ask. Approve. Done.
Pick a shift to see what changes in the product. They play on their own – hover to pause.
Answers about your work, from your data.
Ask about a project, an issue or what the agents are doing. Crux looks up the answer in Redmine before it replies – from the Ask Crux page, the chat bubble on any page, or an @-mention in an issue comment.
The right specialist, automatically.
Crux routes each question to the agent whose skills match – Project Manager, Sales, Support, Time, QA and more. You can also pick an agent yourself.
Changes proposed, never forced.
When a request would change data, Crux shows the exact change as an approval card first. It runs only after you click Confirm.
Bigger goals as work packages.
A work package moves through clear stages – plan, develop, test, review, deliver – with approval gates at the important steps that wait for a person to sign off.
Every run recorded.
Each agent run lands in the Run Ledger with its time, tokens, cost and result. Dashboards show outcomes delivered, spend, what needs your attention and what agents did last.
The specifics, for people who want them.
A full chat workspace.
- Conversations are saved; share one with a teammate as read-only
- Keep useful answers as artifacts
- Each answer shows the model used, tokens and cost
- Chat bubble on every Redmine page – never leave what you are working on
26 ready-made agents in 5 groups – or add your own.
- Project delivery: Project Manager, Scrum, Capacity, Time, Project Setup
- Sales and finance: Sales, Budget, Invoicing
- Support and knowledge: Support, Knowledge Base
- Engineering and quality: QA, Reviewer, Code Reviewer, Test Author, Docs Writer, Monitor, Alert Triage, Root-Cause Analyst, Auto-Fixer, DevOps
- Each agent has a profile: skills, model, monthly spend cap, success rate – pause it or give it its own Redmine identity
Work packages with approval gates.
- Built-in pipelines: Software feature (7 stages, 3 gates), Document (5 / 2), Bug fix (7 / 2)
- Duplicate and adapt any pipeline, or create your own
- Autonomy per work package: suggest-only, execute-with-approval or autonomous
- Approve a gate directly from the work packages page
Safety and budgets.
- Frozen rules – fields no agent may ever change, whatever is approved
- Monthly spending cap per agent; daily chat cap per user
- Crux permissions granted per Redmine role
- Run Ledger with every run’s time, tokens, cost and outcome; technical activity log
Your model, your data.
- Anthropic, OpenAI and Google Gemini built in
- Any OpenAI-compatible endpoint – OpenRouter or a local Ollama server
- API keys kept masked in the Crux key store
- Works with Claude, ChatGPT and Cursor through the MCP server
What Crux changes for each role.
Project Manager
Ask for a project summary and get progress, milestones and risks from live data – then let the Project Manager agent create the follow-up issues, each one confirmed by you.
Engineering Lead
Run a feature as a work package: plan, develop, test, review, deliver – with gates you approve and a work graph of who did what.
Support Lead
The Support agent drafts replies from the knowledge base and proposes ticket updates; nothing is sent or changed without a person’s Confirm.
CTO / IT Director
Frozen rules, budgets per agent and per user, role-based permissions and a complete Run Ledger – AI you can show an auditor.
Crux gets better with these.
Three ways to get Crux.
Crux – self-hosted
- 1 year of support included
- Renew support at 30% per year
- No licence keys · unlimited users · full source
Pick the plugins you need
Add Crux and the plugins it works with on the pricing page – see your one-time total, renewal and 3-year cost.
Build the stack →Redmineflux Cloud
- Crux and every other plugin included
- Fixed price per team size – never per user
- Hosted, backed up and updated by us
Questions teams ask before adopting Crux.
If yours isn’t here, check the pricing page or write to support@redmineflux.com.
Can Crux change data without asking?+
No. In chat, a proposed change is only a card until a person confirms it. Work packages cannot move past an approval gate without a person, whatever the autonomy level. Frozen rules are hard limits that no approval can bypass.
Which AI providers does Crux work with?+
Anthropic, OpenAI and Google Gemini are built in. Any OpenAI-compatible endpoint can be added, such as OpenRouter or a local Ollama server. API keys are stored masked in the Crux key store.
Is Crux available on self-hosted Redmine?+
Yes. Crux is $699 one-time for self-hosted Redmine, with 1 year of support included, and it is included in every Redmineflux Cloud package.
How do we get started?+
Administrators set Crux up once: connect Crux to the Crux core service, add an AI provider and API key, enable the Crux module in each project, grant Crux permissions to the roles that need them, and optionally add agents. After that, everyone can use Ask Crux from the chat bubble on any page.
How much does Crux cost?+
Crux is $699 one-time for self-hosted Redmine – 1 year of support included, then support renews at 30% of the plugin price per year. Or get every plugin hosted on Redmineflux Cloud from $69/month for up to 25 users – a fixed price, never per user.
How is Crux different from the MCP server?+
The MCP server connects external tools such as Claude, ChatGPT and Cursor to your Redmine. Crux is the AI layer inside Redmineflux – chat plus agents with approval cards, pipelines and the Run Ledger. They work together.
Every Redmineflux plugin
Crux running inside your Redmine.
$699 one-time on self-hosted Redmine – or every plugin on Cloud from $69/month.