@bigbongo/cli

Edit your BigBongo app on your own machine and git push to deploy it.

You sign in with your BigBongo account - not GitHub. BigBongo handles GitHub access for you, so you never need a GitHub account. Once you've cloned your app it's all plain git: git commit + git push is the deploy.

Requirements

• Node.js 18+
• git installed and on your PATH

Install

npm install -g @bigbongo/cli

This gives you the bigbongo command.

How to use

1. Sign in

bigbongo login

Your browser opens to a BigBongo approval page showing a short code. Check the code matches, approve, and you're in. Your session lasts 7 days; run bigbongo login again to refresh it or bigbongo logout to sign out.

2. Clone your app

bigbongo clone            # pick your organization, then your app
bigbongo clone my-app     # or name one directly

This clones your app into ./my-app and sets everything up so plain git just works - no tokens or GitHub setup to worry about.

3. Edit and deploy

cd my-app
# ...make your changes...
git add -A
git commit -m "Update the homepage"
git push          # this deploys

Deploys come from the main branch: every push to main is deployed as your app's new live version. After bigbongo clone you're already on main, so a plain git push deploys. If you prefer to work on a separate branch, merge it into main and push to deploy.

There's no separate deploy step - pushing to main is the deploy. git pull and other git commands work normally too.

4. Check on it

bigbongo status   # what's live, and whether a deploy is still in progress
bigbongo logs     # recent logs from your running app

Commands

| command | what it does | |---|---| | bigbongo login | Sign in with your BigBongo account. | | bigbongo clone [app] | Clone your app and set up git access. Name an app, or omit it to pick your organization, then the app. | | bigbongo status | Show what's live (version, commit, URL) and any deploy in progress. | | bigbongo logs | Show recent runtime logs, newest first. Options: --lines <n> (default 50, max 500), --search <text>, --level <error\|warn\|info>. | | bigbongo claude-setup | Point Claude Code at BigBongo, so coding is billed to your BigBongo credits. Options: --org <slug>, --project. | | bigbongo logout | Sign out and clear your local session. |

Run bigbongo <command> --help for details on any command.

If you belong to more than one organization, bigbongo clone asks which organization first, then shows just that org's apps (pick ← Back to organizations to switch). Only organizations that actually have apps are listed, and if all your apps are in one org that step is skipped - there's nothing extra to set up.

Using Claude Code with BigBongo

Run Claude Code on your own machine and pay for it with your BigBongo credits - no Anthropic account and no AWS account needed.

bigbongo login
bigbongo claude-setup
claude

claude-setup writes two keys into your Claude settings: the BigBongo endpoint, and a credential helper. Claude Code then fetches its own short-lived credential whenever it needs one and refreshes it on its own. There is no key to copy and none stored in your shell profile.

Use --project to write .claude/settings.json in the current directory instead of your home settings, and --org <slug> if you belong to more than one organization.

A few things differ from a direct Anthropic connection, and it is better to know them up front than to discover them mid-task:

• Claude Code's built-in web search is unavailable; BigBongo provides mcp__bigbongo__web_search through its MCP server instead.
• Some experimental beta features are turned off, because the upstream provider rejects them outright rather than ignoring them.
• Your prompts travel through BigBongo on the way to the model. Token counts are recorded; prompts and code are not stored.
• When your credit balance reaches zero, requests stop with a message telling you so.

Everything local is unchanged: subagents, hooks, skills, MCP servers, plugins and your CLAUDE.md all behave exactly as they do on any other connection.

If you already have ANTHROPIC_API_KEY set in your shell, remove it - Claude Code prefers it, and it would bill Anthropic instead of BigBongo. claude-setup warns you if it sees one.

How access works

You never handle a GitHub credential yourself. When git needs access, BigBongo issues a short-lived, single-repo token behind the scenes - read access for cloning and pulling, write access for pushing. Your deploys are attributed to you: commits are authored with your BigBongo email, and only pushes from a member of the app's organization are deployed. (If you ever commit with a different email, set it back to your BigBongo email or re-clone.)

Support

Questions or problems? Contact your BigBongo administrator.