# FAQ > Short answers to the questions people ask before and during their first CLI. Short answers, each with a link to the page that covers it in full. ## What can Okibi build a CLI from? One source per generation: a codebase (a local directory or a GitHub repository), a public API docs site, or an OpenAPI document (a file or an https URL). See [Create a CLI](https://okibi.ai/docs/guides/create-a-cli.md). ## What's the difference between okibi and my generated CLI? `okibi` is the tool you use to build and manage CLIs. Your generated CLI, such as `my-cli`, is what you and your users install to call your API. It has its own name, installer, docs, and skill. See [How Okibi works](https://okibi.ai/docs/how-okibi-works.md). ## Does Okibi keep my source code? No. Each build works on your code in its own single-use sandbox, which is never shared or reused and is deleted afterwards. Okibi keeps the generated CLI, its docs, and build logs, which can quote short excerpts of your code. An OpenAPI file you upload is stored with the CLI so it can be regenerated. See [How Okibi handles your code](/security). ## Who owns the generated CLI? You do. The [Terms of Service](/terms) say you own the CLIs and other artifacts Okibi generates for you. You are responsible for reviewing them before you rely on them. ## Can I edit the generated code? Yes. `okibi pull ` downloads the full project, and the source also lives in a private repository. Commits on that repository's default branch can ship as the next version: ```sh okibi clis changes my-cli okibi clis publish my-cli ``` Publishing needs the owner or admin role. See [Releases and install](https://okibi.ai/docs/guides/releases.md). ## Can I keep the code in my own GitHub account? Yes. In the project's **Settings**, under **Where it lives**, click **Move to GitHub** next to **Code** and choose **Your GitHub** instead of **Okibi-hosted private repo**. From the terminal, connect the publisher app with `okibi auth publisher`, then run `okibi clis hosting target my-cli github --account OWNER`. The publisher app is separate from the GitHub App that reads your repositories. ## Which platforms does the generated CLI run on? macOS, Linux, and Windows, each on x64 and arm64. Okibi builds every release for all six, so your users don't need Go or any other toolchain. macOS and Linux use the `sh` installer; Windows uses the PowerShell one. ## Does the generated CLI work with agents and MCP? Yes. Every release includes a SKILL.md, and the installer adds it to the coding agents it finds. Every release also gets a hosted MCP server, so agent clients can use the CLI without installing it. See [MCP server](https://okibi.ai/docs/guides/mcp.md) and [Skill and generated docs](https://okibi.ai/docs/guides/skill-and-docs.md). ## Can a coding agent drive okibi for me? Yes. The okibi installer adds an okibi skill to your agents, and `--agent` turns off prompts and returns JSON where supported. See [Set up with your agent](https://okibi.ai/docs/set-up-with-your-agent.md) and [Agent and CI mode](https://okibi.ai/docs/cli/agent-mode.md). ## What happens to my live CLI when a build fails? Nothing changes for your users. If a build fails, the previous release stays available. See [Troubleshooting](https://okibi.ai/docs/troubleshooting.md#build-failed). ## How do I delete a CLI? You need the owner or admin role. **In the app** Open the project's **Settings**. Under **Danger zone**, click **Delete**, type the project's name to confirm, then click **Delete** again. **In the CLI** ```sh okibi clis delete my-cli ``` okibi asks you to type the CLI's name. It refuses to run with `--agent`, so a person has to do it. Deleting removes the CLI, its docs, and its build history. Installed copies keep working but stop getting updates.