Build and update a visual operating cockpit for AI-native solo founders.
A visual operating cockpit for AI-native solo founders.
One Person Company OS helps one founder turn an AI product idea into a company that can be inspected, advanced, and handed off between sessions. It keeps the business loop visible:
promise -> buyer -> product capability -> delivery -> cash -> learning -> asset
The first workspace is built around the questions a solo founder actually needs to answer today:
Generated workspaces use three output layers:
artifacts/ or 产物/Chinese founders get:
阅读版/00-经营驾驶舱.html视觉素材/business-loop.svg视觉素材/revenue-pipeline.svg视觉素材/ai-image-prompts.mdEnglish founders get:
reading/00-operating-cockpit.htmlvisual-kit/business-loop.svgvisual-kit/revenue-pipeline.svgvisual-kit/ai-image-prompts.mdThe hidden machine state stays at .opcos/state/current-state.json.
Python 3.7+scripts/ensure_python_runtime.py prints compatibility and manual install guidance onlypython3 scripts/preflight_check.py --mode create-company
python3 scripts/ensure_python_runtime.py
python3 scripts/init_business.py "North Star Lab" --path ./workspace --product-name "North Star Assistant" --target-user "independent builders" --core-problem "they need one visible loop for product, revenue, delivery, and cash" --product-pitch "a visual operating cockpit for one-person AI companies" --language en-US --confirmed
python3 scripts/validate_release.py
clawhub install one-person-company-os
I am building a one-person AI company. Use one-person-company-os v1.0. First help me confirm the sellable promise, first buyer, and core problem. Then create the approved local workspace, open with the operating cockpit, show the current bottleneck visually, and save only approved files inside that workspace.
python3 scripts/validate_release.py
It validates the state model, localized workspaces, operating cockpit, visual assets, DOCX-only artifact directories, role/template language, and public release materials.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
docker run -i --rm ghcr.io/living-hi/one-person-company-os-mcp:1.0.3Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-living-hi-one-person-company-os": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/living-hi/one-person-company-os-mcp:1.0.3"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referenceghcr.io/living-hi/one-person-company-os-mcp:1.0.3dockerOne Person Company OS works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.