No knowledge files yet.
Click 🧠 Analyse project to have Claude explore the codebase and write CLAUDE.md + docs/knowledge/ — structure, nuances, and gotchas that every future session (and board card) loads automatically. Board cards also add to these files as they discover things while working.
Publish log
Git graph
Past conversations
Project config
Project servers
Save database and application access, then select a profile on a card. External access must also be allowed on the card. Production profiles prohibit automatic migrations and seeding.
Deploy through your Server Manager account
Connection settings belong to your profile. Choose hosts when publishing.
Opt-in. Credentials remain on the hub; a planning card receives a short-lived, command-allowlisted proxy token. Requires a valid Public base URL in system email/URL settings.
Planning runs may use raw SSH with card-provided credentials. Read-only behavior is a prompt contract, not enforced by the hub.
ServerManager interoperability is managed through Jarvis. A root administrator can enable this for the project. Choose the Docker host in the card editor. Planning remains read-only.
Values are stored on the hub and supplied only to eligible database-enabled job environments. Prompts and prompt snapshots receive variable names only, never their values.
Opt-in for Claude planning and implementation runs. Use read-only database accounts. Read-only behavior is a prompt contract, not enforced by the hub.
Plan AI
Choose whether cards use a read-only research handoff before implementation. Merge cards always run the Implementation AI directly.
Controls the length of Plan and Implementation AI explanations. Concise keeps file-level steps and verification.
Implementation AI
Receives the persisted Plan AI handoff and writes the code. Leave unset to use the Plan AI and its settings.
Choose an economical planning model and a balanced implementation model. Applies to cards inheriting project settings; explicit card choices and resumed conversations keep their models. Planning and approval requirements stay the same.
Work board
Additional projects (none)
Spec
The implementation card is built from this plus the transcript.Soundboard
New card
Use these credentials if required to run and test the platform.
Additional projects (none)
Credentials
Assign saved credentials without putting secrets in the details. Names and descriptions are shared with the AI; secret values are available to its commands.
Documents
Card
Apps
Google Play connections
Service-account keys stay on DevHub and are never written into the repository.
Android apps
One profile per branded MAUI project. Builds run sequentially on each project’s assigned agent.
Release history
Google review status refreshes automatically every two minutes.
| App | Version | Track | Status | Created | Artifact |
|---|
iOS release automation
The Apps workspace is ready for iOS, but automatic IPA signing requires an App Store Connect API key and a macOS build agent. Android can be used now without changing the existing iOS scripts.
Connect Google Play
Add Android app
Agents
| Status | Name | Company | Machine | Version | Claude CLI | Codex CLI | Gemini CLI | Runway | Jobs | Max jobs | Weight | Voice operator | Usage (month / 5h) | Last seen |
|---|
Add API endpoint
Add container registry
Console
connecting…
File
Agent key
Paste this key into the agent app on the target PC. You can view it again later with Show key.
Dashboard
Tokens per day
Jobs completed per day
Cards by hour
Projects
| Project | Jobs done | Active | Tasks | AI time | Tokens | Tokens (all time) | Est. cost |
|---|
Agents
| Agent | Jobs done | Running now | AI time | Tokens in | Tokens out | Est. cost |
|---|
Settings
Branding
Models
Claude models
Codex models
Gemini models
What each model is best for
AI fallbacks
AssemblyAI transcription
Duplicate detection
Usage & results
Email (SMTP)
Send a test email
Single sign-on (SSO)
Microsoft
API endpoints
| Name | Type | Base URL | Default model | Key |
|---|
Container registries
| Name | Host | Username | Password |
|---|
Credentials
Store reusable secrets here, then assign them to cards. Keep names and descriptions free of secrets.
| Name | Environment variable | Description | Updated |
|---|
Documents
| Title | Projects | Size | Updated |
|---|
Continuous testing
Every project. Every spare agent. A continuous cycle of testing, evidence and improvement.
Select a test project
Choose a project to view settings, findings, submissions and live activity.
Opportunities
Spare agents research the market, investigate useful ideas and prepare plans for your approval.
Research coordinatorShares spare capacity with continuous testing
Research pool & review queue
Give agents product direction, then review their sources and proposed plans.
Security
NuGet and npm dependencies are checked after implementation runs and every Sunday at 03:00 (server time). Manual and weekly scans use the latest default branch. Failed or incomplete scans retain known findings.
Build feedback
Every round of a Chicane build feedback loop: what arrived, what was asked of the assistant, what it replied and what was answered. The correlation id matches the one on Chicane's Integrations tab. Kept for 90 days.
System users
Developers who use the hub. Until the first user is registered the hub is open; after that, sign-in is required. Each user is scoped to projects and granted action permissions.
| Name | Company | Role | Projects | Permissions | Status | Last login |
|---|
Companies
Companies isolate users, projects, agents, and Azure DevOps connections. Root is the existing default company.
Email log
| Date/time | To | Subject | Status |
|---|