Get comfortable with BitCadence
Give your AI helpers a clear job. See what is happening. Stay in control of what happens next.
Start with the short guides below. The complete references are here for a particular command, option or screen.
Your first useful task
- Install and open BitCadence. Start the local gateway and open the console. Prefer the Windows desktop app for a window and tray icon.
- Connect the console. Demo mode is simulated; a connected console works with your real board.
- Connect an AI app and check Helpers. Connecting an app and having a worker ready to take jobs are different steps.
- Ask for something. Describe a small task, inspect the proposed steps, then approve and start. Drafting alone does not run the plan.
- Follow the result on Home. Approve only what you intend to authorize, then inspect the recorded result.
Prefer a single walkthrough? From installed to your first result takes you through it. Prefer the terminal? Everyday commands covers the short words.
What would you like to do?
| Your goal | Start here |
|---|---|
| Find what needs you | Home and Approvals |
| Give a helper a task and inspect the result | Job board |
| Add a helper or understand its light | Helpers and worker setup |
| Group work into a project | Projects |
| Repeat a task | Schedules |
| Share facts between helpers | Drumline memory |
| Follow a longer autonomous run | Live Score and Score contracts |
| Change a setting or fix a connection | Settings and configuration |
| Understand a control's effect | Every screen and control |
| Find an exact command, argument or flag | Complete CLI reference |
Three things that make the system easier
- Choose one everyday interface. The console is the main browser workspace. The desktop manager runs local services. The smaller
/dashboardis a separate interface; the GUI reference explains which controls live where. - Start small and check the outcome. A drafted plan, a submitted job, an online worker and completed work are different states. Look for a recorded result before calling a task finished.
- Keep advanced details close, not in your way. Open advanced controls when a task needs them. The references keep the detail available without making every first step technical.
Explore safely
The console labels simulated data Demo. Use it to learn the layout; it does not prove a real worker is connected. Do not put real credentials into examples or screenshots. Copying a documentation code block only copies its text.
Approval, pause, retry, token and deletion controls can change real work. Read the relevant guide first. Pause everything can halt active attempts; it does not promise that in-progress work will finish.
Coverage and product review
- Coverage and verification records the checked command/control inventories and runtime limitations.
- Usability review gives concrete ways to make the product clearer, safer and easier to enjoy.
BitCadence Core is source-available under the Prosperity Public License 3.0. Existing integrations keep mco, MCO_* settings and ~/.mco/ paths; the product name change does not require renaming those interfaces.