Improve adoption

These suggestions match the tips in each dimension's detail panel on the Usage page. Start with the dimension that's lowest. See AI adoption score for how each one is measured.

Frequency: make Hull a daily habitCopy Anchor Link

• Expand beyond the editor. A lot of work happens in the terminal. Install the Hull CLI so people can use Hull for scripting, Git work and debugging too.
• Start with autocomplete. It needs no prompting and builds daily use for boilerplate, repeated patterns and test scaffolding. See Autocomplete.
• Tie Hull to existing routines. Stand-up prep, quick explanations of unfamiliar code, pull request descriptions and commit messages add up faster than occasional big tasks.

Depth: chain agents into real workCopy Anchor Link

• Chain your workflow. Plan a change, implement it, then run code review on the result. Using the agent, a cloud agent and code review on the same day is what the multi-agent chain signal counts.
• Give Hull better context. If suggestions miss, turn on codebase indexing and add an AGENTS.md with your conventions.
• Make output easy to verify. Clear test commands and a working build let agents check their own work, which builds trust.

Coverage: broaden the rolloutCopy Anchor Link

• Introduce more surfaces. Coverage rewards people who use several kinds of agent: the in-editor agent, autocomplete, cloud agents and code review.
• Activate unused seats. Check the Organization page for members who haven't started. A short walkthrough or pairing with an experienced teammate often helps.
• Spread usage across the week. Making code review part of every pull request naturally spreads activity across days.

Running an adoption pushCopy Anchor Link

1. Set a baseline. Note the current score and each dimension.
2. Pick one dimension and one or two actions from above.
3. Pick a champion on each team who uses Hull well and can show others.
4. Check the trend every week or two, and adjust.

Things that tend to backfire:

• Mandating usage levels. It creates resentment without building habits.
• Focusing only on power users and ignoring people who haven't started.
• Measuring without acting on what you see.
• Using individual scores for performance reviews.

Enterprise: feature adoptionCopy Anchor Link

Enterprise organizations also get a Feature adoption view on the Usage page. It checks whether the organization has set up features such as source control, Code Reviewer, Security Agent, a team workflow integration and Cloud Agent, and lists Recommendations for what to turn on next. Owners and admins can dismiss recommendations that don't apply.