ArxDeck Helper
The setup assistant agent for workflows, agents, GitHub, webhooks, feedback, Publish, and more via proposals.
ArxDeck Helper
ArxDeck Helper is a built-in setup assistant that helps you configure ArxDeck through conversation. It does not apply changes directly — it creates proposals you review and approve. Approved changes (and matching UI saves) are recorded in per-entity History with diffs and restore — see Configuration revision history.
Helper and its setup capabilities are available in every project — no separate installation step. Helper is the curated default for setup chat (bundled skills, entry points, and default MCP allowlist). Other agents can also use Configuration MCP tools when a platform admin allowlists them and the current user has the required permissions.
What Helper can configure
Through chat, Helper can propose changes to:
- Agents — providers, capabilities, MCP allowlists, prompts, skills
- Workflows — statuses, automations, task templates, work queue groups, status↔agent bindings, custom field definitions inline on the workflow
- Scheduled tasks — calendar or interval jobs with task templates
- Skills — agent instruction packs exposed via MCP
- Content modules — module metadata and resource manifests (superadmin scope)
- Project settings — general settings, capability toggles via proposals
- Project templates — create presets for new projects
- Ticket views and labels — saved filters and label catalog entries
- Knowledge types — type definitions and mutation modes
- GitHub settings — repository connection, docs paths, agent starting ref, CI workflow (binding proposals redirect through OAuth)
- Inbound webhooks — endpoints, extractions, routes, and webhook tasks
- Feedback settings — ingest tokens and capability configuration
- Publish / deployment settings — application config, auto-deploy, staging, secret metadata (secrets collected in approval UI only)
Helper can search published content modules and explain installation state, but it does not auto-install modules for you. Platform admins can browse the full module catalog (list_platform_modules_config) and propose manifest bindings plus publish/archive lifecycle actions.
Helper can discover MCP attach options via list_mcp_tools_config (internal ArxDeck tools plus org external servers) and model ids via list_agent_provider_models_config when configuring agents. Use get_config_permissions to check what you can propose before calling propose_*_config.
How to start
| Entry | What happens |
|---|---|
| New helper chat in the chat launcher | Opens a private conversation in the header chat modal (same overlay as New chat); optional Include current page context shares the current page URL and resource when detectable |
| Help me set this up on admin pages | Opens helper chat with context banner and descriptive title; waits for your first message |
| Fix it on a failed config proposal | Opens helper chat with proposal context and starts a turn immediately |
| New chat picker | Lists ArxDeck Helper |
Helper conversations are private — only you can read and send messages in that thread.
When entry context is set, Helper receives page URL, resource type and id, and instructions to load full configuration via MCP before proposing changes. A read-only banner in the chat shows the same context.
Approval flow
- Helper calls MCP propose tools with a full validated payload.
- You open Project → Proposals (or platform Proposals for global items).
- You approve or reject. Invalid payloads are blocked at propose time with field-level errors. Workflow updates must omit read-only managed binding automations (
managed: trueinget_workflow_config); usestatusAgentBindingsfor binding changes. - Approved changes appear in the resource's History page with actor, source, and diff.
To revise a pending proposal, propose again — the newer proposal supersedes the older one.
Setup & configuration
Ensure project members who should configure via Helper have permission to approve proposals (project admin for most configuration; platform admin for global resources).
To give other agents MCP access for ticket work (not setup), configure those agents separately under Settings → Agents.