Local-first · Approval-gated workflow · companyturbo.link

An AI company that runs on your PC—with safety valves built in.

CompanyTurbo runs autonomous company workflows locally on your machine. Launch the local Web UI (127.0.0.1) from the CLI to review jobs and approvals: external sends, posts, and spending require approval by default. The email / X / Instagram connectors really send and post after approval once you connect credentials; while unconnected they run in dry-run mode (audit log only).

curl -fsSL https://companyturbo.link/install.sh | sh How to install Try Local UI Preview
Execution Scope

UI, scheduler & SQLite run locally (127.0.0.1)

Default Guardrails

AutoMode OFF · Approval-gated · ¥0 spend limit

Current Stage

Connectors implemented (dry-run until connected) · Paid plan in preparation

How to Get CompanyTurbo (Install)

The general release is distributed via the installer on this site (the source repository is private). Run this single line in your terminal:

curl -fsSL https://companyturbo.link/install.sh | sh

  • Environment: runs on macOS / Linux (Windows is unverified). You need a terminal with sh and curl.
  • bun: bun (1.3.x) is required to run. If it is not installed, the installer will guide you through (or perform) the bun installation. Piped execution reads confirmations from /dev/tty, so in environments without an interactive terminal, pass --yes (e.g. curl -fsSL https://companyturbo.link/install.sh | sh -s -- --yes).
  • AI CLI: business inference uses the Claude Code CLI (claude) or Codex CLI (codex) already installed on your PC (check detection with companyturbo doctor).
  • SHA-256 verification: the downloaded package (tarball) is verified against its SHA-256; on mismatch nothing is extracted and the install aborts.
  • License: installing means you agree to the Terms of Service (End User License Agreement).
  • Install location: the app is installed to ~/.companyturbo/app and the companyturbo / rc commands to ~/.companyturbo/bin (you will be told if your PATH needs updating). Data (DB, credentials) is stored in ~/.companyturbo.

Start

Run companyturbo (or rc) to start the local server (127.0.0.1:7777); the dashboard opens in your browser. Use companyturbo doctor to check claude / codex detection.

Update

Run the installer again (the same command) to safely switch to a new version (it is swapped in from a verified temporary directory, so on failure the previous version remains; the data directory holding your DB and credentials is never touched).

Uninstall

companyturbo stop (stop first if running)
rm -f ~/.companyturbo/bin/companyturbo ~/.companyturbo/bin/rc ~/.companyturbo/bin/rollingcompany
rm -rf ~/.companyturbo/app
Only if you also want to delete your data (DB, credentials, etc.): rm -rf ~/.companyturbo

Local Web UI Preview

A conceptual interactive preview of the local dashboard launched from the CLI. AutoMode starts OFF, and external send actions wait in the approval queue until you approve or reject them.

CompanyTurbo 127.0.0.1:7777
AutoMode OFF (default)

Approval Queue (2)

Preview simulation: runs purely in your browser (no real send, post, or spend)

Policy & Spend Limits (Defaults)

read auto
send (external messages / posts) approval
spend (monetary spend) approval
Daily / Monthly Spend Limit ¥0 / ¥0 (blocked until configured)

Audit Log (SQLite preview)

Note: This widget simulates the local dashboard behavior purely in your browser; the preview itself makes no network requests (page analytics are measured with Cloudflare Web Analytics as noted in the footer). In the actual product, external send actions are approval-gated by default: unconnected connectors run in dry-run (log only), and connected connectors really send or post after approval.

How It Works

The Web UI, scheduler, approval queue, and SQLite audit log run locally on your PC. Prompt inference delegates to your installed local CLIs (claude / codex), so inference and prompt transmission depend on each CLI's configured endpoint.

STEP 01 CLI + Web UI

Start Locally from CLI

Launch a loopback server on 127.0.0.1 and the local Web UI directly from the CLI. State, jobs, reports, and audit entries are stored locally in SQLite.

STEP 02 AutoMode

Autonomous Loop & Job Queue

Onboarding (implemented) registers the company and owner name, researches the owner profile, lets you pick a business idea, and queues prioritized initial jobs. While AutoMode is ON, the periodic scheduler runs cycles: assess state, create next jobs, run queued work, and record cycle reports.

STEP 03 Provider CLI

Isolated Local CLI Providers

Detects installed Claude Code CLI (claude) and Codex CLI (codex) automatically via the CLI diagnostic check and passes prompts over stdin (inference runs against each CLI's configured endpoint). When no CLI is available, onboarding falls back to built-in starter job templates.

Safety Design (Implemented Guardrails)

Every autonomous loop is constrained by fail-closed policy checks, conservative defaults, and immediate kill switches.

Approval-Gated External Actions

Actions are categorized as read (auto), send (approval), or spend (approval), configurable to auto, approval, or deny. Risk comes strictly from connector definitions—never from LLM self-reports—and unknown actions fail closed.

AutoMode OFF by Default & Backpressure

AutoMode starts disabled so nothing executes automatically on startup. When 5 or more jobs are awaiting approval, the scheduler stops creating new jobs until pending items are resolved.

Daily & Monthly Spend Limits

Spend limits (JPY) default to 0, blocking all spending until explicitly raised. Checks sum recorded spend, reserved pending approvals, and the new amount—and re-verify at the moment of approval. Send actions also have a daily send cap (default 5 for auto-approved sends) plus per-channel caps (e.g. email 20/day and 5/hour, X posts 10/day, Instagram 5/day; configurable), re-checked at approval and right before sending.

One-Action Emergency Stop

Clicking Emergency Stop in the UI or running the CLI emergency-stop command turns AutoMode OFF, cancels existing queued, running, and awaiting-approval jobs, rejects pending approvals, and aborts provider subprocesses for active jobs (the CLI stop also terminates the running local server). Even if triggered while the scheduler is awaiting a planning response, the arriving plan is discarded and no new jobs are created after the stop.

Per-CLI Isolated Execution

claude runs with built-in tools and external MCP disabled (--tools "" / --strict-mcp-config); codex runs in a read-only sandbox ignoring user config (-s read-only / --ignore-user-config). Both execute inside an isolated empty sandbox directory.

Loopback-Only UI & Full Audit Trail

The server binds only to 127.0.0.1 with strict Host and Origin verification against DNS rebinding and CSRF. State-changing APIs are protected by a per-launch token (stored in a 0600-permission file). LLM text is rendered via textContent only, and every state change is logged to SQLite. Credential and data files are also protected with 0600 / 0700 permissions.

Current Status: The email (Gmail API / SMTP), X, and Instagram connectors are implemented and really send and post after approval once credentials are connected. While unconnected they run in dry-run mode, recording only what would have been done to the audit log (Meta Ads is a dry-run stub for now; artifact-site publishing is also dry-run until the operator-side publishing API is configured).

Integrations & Publishing

The email / X / Instagram connectors and artifact-site publishing are implemented. Artifact-site publishing is a paid-plan feature still in preparation, which is marked as such below.

External Connectors

Implemented (dry-run until connected)

The following three connectors are implemented. Once you connect credentials (developer app client id/secret or tokens), they work for real; while unconnected they run in dry-run mode and only record to the audit log.

  • Email (implemented): Send email via Gmail API or SMTP, read inbox with Gmail (sending is approval-gated by default)
  • X (implemented): Read timeline, publish posts and DMs (approval-gated by default)
  • Instagram (implemented): Read insights, post photos (approval-gated by default)

Artifact Site Publishing

Implemented · Preparing for the paid plan

Websites and landing pages generated by your AI company can be published directly to dedicated subdomains — implemented. As a paid-plan feature, rollout to users is still in preparation.

  • URL pattern: https://<name>.companyturbo.link
  • CompanyTurbo's management UI stays strictly on your local machine (127.0.0.1), separate from published artifact sites.
  • AI-initiated publishing actions are categorized as external sends and require approval by default (until the operator-side publishing API is configured, it runs in dry-run and no live deployment happens).

Plans

We plan to offer a free local CLI tier and a paid tier with hosted LLM connectivity and artifact-site publishing. Pricing has not been finalized yet.

Free Plan

Local CLI

Free

Run CompanyTurbo on your own computer using local AI CLIs you already have installed.

  • Uses local Claude Code CLI (claude) or Codex CLI (codex)
  • Local Web UI (127.0.0.1) and SQLite audit log
  • Approval queues, spend caps, and emergency stop included

Paid Plan (Planned)

Planned · Pricing TBD

Pricing TBD

Designed for users who want hosted model access and artifact-site subdomain publishing without managing everything via local CLIs.

  • Hosted LLM connection (Planned)
  • Artifact site publishing (<name>.companyturbo.link): implemented, in preparation
  • Details and pricing will be announced once finalized

Availability & FAQ

Current release status and key architectural questions.

Q. How can I download or install CompanyTurbo?

Get it from the installer on this site: curl -fsSL https://companyturbo.link/install.sh | sh (see How to install above for the environment requirements and detailed steps). The package is SHA-256 verified, and installing means you agree to the Terms of Service (EULA).

Q. Which OS and environment are supported?

It runs on macOS / Linux (Windows is unverified). You need bun (1.3.x; the installer guides you through or performs its installation if missing) and, for business inference, the Claude Code CLI (claude) or Codex CLI (codex).

Q. How do I update or uninstall?

To update, just run the installer again (the same command swaps in the new version). For uninstall, a short procedure is provided in How to install (stop with companyturbo stop, then remove the commands and the app itself).

Q. Could the AI send emails or post to social media without my permission?

By default, AutoMode starts OFF, external send and spend actions require approval, and the spend limit is ¥0 (policies can be adjusted in settings). With connected credentials, approved actions really send and post; while unconnected, connectors run in dry-run mode (log only).

Q. If the app runs locally, what is companyturbo.link for?

companyturbo.link is the official home page introducing CompanyTurbo (and may later host a web dashboard page). Artifact sites built by AI companies are published separately under <name>.companyturbo.link — the feature is implemented, as a paid-plan offering still in preparation.

Q. Which local CLIs are supported, and how are they sandboxed?

Claude Code CLI (claude) and Codex CLI (codex) are supported. claude is invoked with built-in tools and external MCP disabled, while codex is invoked in a read-only sandbox ignoring user config inside an empty working directory. Prompts are sent to each authenticated CLI's configured endpoint for inference.