Gentlybot docs

Workspace controls

Workspace settings give owners and admins a safe baseline for how new work starts, which systems can act, and where runs execute.

Owner or admin

Thread defaults

Choose the starting behavior for new threads across the organization.

  • Starting mode
  • Automatic commits and pull requests
  • Whether code review runs, how deeply, and how many correction loops it may use
Owner or admin

Code review policy

Choose which reviewer dimensions should inspect changes before they are handed over.

  • Organization-wide reviewer selection
  • Normal or deeper review through thread defaults
  • Visible review results in the thread
Owner or admin

GitHub installations & capabilities

Control repository access and opt into event-driven GitHub behavior.

  • Connected accounts and selected repositories
  • Separate capability switches, off until enabled
  • Permissions and events shown next to each capability
Owner or admin

Models & AI credentials

Use the included defaults or decide which models should handle different kinds of work.

  • Editable pools for Ask, Small Coding, and Complex Coding
  • Ordered fallbacks, reasoning level, and speed
  • Optional workspace-owned provider credentials
Owner or admin

Runtime

Manage the compute available to the workspace, including connected Desktop machines.

  • Runtime providers and nodes
  • Desktop connection and availability
  • Where a new thread runs through the composer runtime picker

Prompt review

Ask Gentlybot to review recent prompts and email a private coaching report.

  • Choose a 7, 14, or 28 day window
  • See what already works and rewritten examples
  • Admins can request a review for another member; the result is emailed to the requester

Defaults do not rewrite existing threads

Thread defaults apply when new work is created and only to people who have not chosen their own composer defaults. Changing the workspace baseline does not silently alter a thread that is already underway.

1

Start conservative

Default new threads to Auto or Ask, keep automatic pull requests off, and review the first few Implement runs closely.

2

Turn on one capability at a time

Enable a GitHub automation or deeper review only for a workflow with a clear owner and an obvious success condition.

3

Tune from evidence

Use thread results, prompt coaching, model usage, and reviewer findings to change defaults instead of guessing up front.

Reviewing and iterating Integrations setup