Settings

The settings page is where operators define how ainative-business authenticates, which tool requests can be trusted by default, how much provider activity is allowed to cost, and how the local workspace data should be managed.

Settings with Providers and Runtimes, task routing options, Anthropic OAuth, OpenAI API, and Ollama local models
Providers and Runtimes with task routing selector, Anthropic and OpenAI connected status, and Ollama local models

Key Concepts

  • Providers & Runtimes — Configure authentication for all five provider runtimes from one section with task routing preferences (Latency, Cost, Quality, or Manual).
  • Ollama Local Models — Connect to a local Ollama instance for free, private AI execution. Test connection, discover available models, pull new ones, and integrate with smart routing.
  • Permission Presets — Three composable tiers — Read-Only (low risk), Git-Safe (moderate), and Full-Auto (high) — each with risk badges. Higher tiers include all lower-tier permissions.
  • Default Tool Permissions — Seed safe approval patterns so the inbox does not need to mediate every low-risk action. Patterns can be broad (Read) or specific (Bash(command:git status)) with wildcard support.
  • Delivery Channels — Connect Slack, Telegram, or webhook endpoints for outbound notifications and bidirectional chat. Each channel card shows Chat/Active/Test/Delete controls.
  • Cost & Usage Guardrails — Configure daily and monthly spend caps plus runtime-specific token/spend limits with pacing meters.
  • Browser Tools — Independent toggles for Chrome DevTools and Playwright automation; read-only browser actions auto-approved within the trust tier.
  • Chat Defaults — Choose the default AI model for new conversations with cost-tier indicators so operators can balance capability against spend.
  • Task Resume — Retry failed or cancelled tasks with a 3-attempt limit, resuming execution from a known state instead of starting over.
  • Data Management — Seed sample data for evaluation or clear all data (respects table relationships) when resetting the workspace.
  • Local-First Configuration — Settings are managed close to the workspace instead of hidden inside a remote SaaS control plane.

The Providers & Runtimes section manages connections for Anthropic (OAuth or API Key), OpenAI (API Key), and Ollama (local endpoint). A task routing selector lets operators choose between Latency, Cost, Quality, or Manual mode to control how ainative-business picks a runtime when creating tasks.

Settings authentication with Claude OAuth and API Key methods, OpenAI Codex Runtime configuration, and connection test buttons

Authentication Methods

MethodDescriptionBest For
Anthropic OAuthBuilt-in sign-in flow for Claude subscriptionsIndividual operators and local evaluation
Anthropic API KeyDirect credential entry for Claude Agent SDK and Direct APIDevelopment, testing, and controlled server setups
OpenAI API KeyProvider-aware credential entry for Codex App Server and Direct APIDual-runtime workspaces and OpenAI-backed runs
Ollama (Local)Connect to a local Ollama instance for free, private inferencePrivacy-sensitive work and cost-free experimentation

Cost Guardrails

Budget configuration with monthly spend cap, Claude/Codex provider allocation slider, and latest pricing table
Budget allocation with provider spend splits, Claude billing plan, and latest provider pricing table
Live spend pacing with monthly and daily caps, provider breakdown, and permission presets with risk tiers
  • Overall Daily / Monthly Caps — Limit total paid activity across runtimes in the current day or month window.
  • Runtime-Scoped Caps — Apply spend or token ceilings to Claude or Codex independently when one runtime needs tighter control.
  • Blocked-State Visibility — Settings shows whether a budget is currently blocking new work and when the next reset happens.
  • Warning Notifications — The inbox can warn operators as active budget windows approach a configured threshold.

Data Management

Permission presets with Read Only, Git Safe, and Full Auto risk tiers, tool permissions, and data management
  • Clear All Data — Removes projects, tasks, workflows, schedules, documents, logs, notifications, and seeded profiles while preserving the underlying setup.
  • Permission Pattern Curation — Operators can review and revoke auto-approved command patterns from one place.

Instance & Upgrades

The Instance section surfaces metadata about this installation: the stable instanceId, the current instance branch (e.g., local for single-clone users, or a named branch for private instances), the upstream remote it tracks, and whether the first-boot bootstrap has completed.

  • Upgrade Detection — An hourly scheduled poll runs git fetch against the upstream remote and compares HEAD to origin/main. When upstream is ahead, the sidebar shows a small Upgrade available badge next to Settings and the Instance card surfaces a “New version available” indicator with the number of commits behind. Detection is git-based rather than GitHub REST to avoid rate limits.
  • Upgrade Session — Clicking Start upgrade opens the upgrade session as a right-side sheet — not a full-page navigation — so you can glance back at your workspace while the upgrade runs. The session is backed by a task row with the upgrade-assistant profile, reusing the full execution infrastructure: approval caching, SSE log streaming, and inline conflict resolution via a 3-card cluster (Keep mine / Take theirs / Show diff).
  • Footer Upgrade Button — A subtle Upgrade button appears in the sidebar footer once an upgrade is available, opening the same upgrade session sheet from any page.
  • Dev Mode Gate — When AINATIVE_DEV_MODE=true is set, the Instance section displays a “Dev mode” banner and the upgrade machinery is intentionally bypassed, protecting contributor repos from having a pre-push hook installed by the bootstrap flow.

How It Works

Settings centralize the trust model for the rest of the product. The authentication section controls how runs are authorized, the permissions section shapes inbox volume, the budget section controls runtime expansion, and the data tools make it possible to reset or repopulate the workspace safely.

The visible grouping also keeps operational choices legible. You do not have to remember where an approval rule lives, which runtime is authenticated, or why paid work is blocked; all of those controls stay explicit on one screen.

Use Cases

Team Onboarding Setup

Product Team · Getting new team members started in under 5 minutes

A new teammate connects with OAuth, reviews the default approval patterns, and resets the sample workspace before starting real work. Setup stays legible because the auth, permission, and data controls are grouped together.

API Key Rotation

Developer · Monthly credential rotation for security compliance

Your security team rotates access monthly. You update the auth mode or credential, remove any stale auto-approval patterns, and keep the control surface for trust decisions in one place.

Starting Fresh

Non-Technical User · Resetting after initial experimentation

You spent a week exploring seeded sample data. When it is time to move to production work, one reset clears the operational records while leaving the product ready for a clean start.