1. Overview — what we are building#

CPU AI (Coding Power Unit AI) is a developer workspace that helps people turn ideas into understandable, reviewable software work. Today it combines a Google-connected free AI chat, coding project editor, code inspection tools, a lightweight agent configuration studio, a planning workflow builder and a personal dashboard.

We are not yet a fully autonomous coding agent, hosted IDE, Github write-back service or a blockchain launchpad. CPU emphasizes human review before any future automated changes.

Product pillars

• Accessible AI: A simple Google sign-in and a small free AI allowance. No personal AI API key is required for the Free AI product.
• Practical developer tools: Work with local files, review code, inspect public repositories and compare changes before using them.
• User control: Keep editable project work local unless you explicitly share a prompt with AI; avoid executing or committing changes without explicit approval.
• Transparent capabilities: Clearly distinguish live browser utilities from optional operator features and roadmap proposals.
• An open ecosystem in the future: Optional agent sharing, collaborative bounties and governance, if developed and reviewed.

2. Mission, vision and values#

Mission: Make trustworthy AI-assisted development approachable, affordable and understandable for builders at different skill levels.

Vision: An AI development hub where users can move from a question to a reviewable implementation, work across coding tools and eventually collaborate with specialist agents and a community — while retaining approval over their source code.

Values: Clarity over hype; privacy-aware design; understandable outputs; cost transparency; human review; honest product status.

Tagline (proposed): Build Smarter. Create Faster.

3. Features and availability#

Availability in code does not by itself confirm the latest production deployment.

4. Start here: your first AI conversation#

1. Open Free AI Chat ↗ or type a prompt on [Home](/). A Home prompt is carried over as a draft, not automatically submitted.
2. Select Sign in with Google. Your Google account authenticates your CPU profile; it does not provide a free Google Gemini API allowance.
3. The account sidebar should show your name and today's free messages.
4. Type a coding question or choose a prompt suggestion (review code, plan an app, debug an API).
5. Optionally attach a small text/source file. Remove confidential code and credentials first.
6. Click Send message (or Ctrl/Cmd + Enter). The message is sent to CPU's backend and processed by Cloudflare Workers AI.
7. Read the answer, review any code, and use Copy code, Copy message or Export .md.
8. Choose New chat for a separate topic. If the history database is configured, your latest conversation can be reopened later.

Free quota: 5 model requests per account per UTC day; resets at 00:00 UTC. This is an application-level quota, not a promise of guaranteed inference capacity. All users share the Cloudflare Workers AI allocation; requests can fail if capacity or provider limits are reached. Answers may be inaccurate, especially when reviewing security-sensitive code.

File handling: Free AI accepts small text/source file attachments (maximum 10 KB) and includes up to 1,700 characters of the selected file. Requests are capped at 2,500 characters per message; shorten the prompt if needed. Attachment content is sent only when you explicitly click Send.

Saved conversations: If the conversations table exists in Cloudflare D1, the service saves a limited conversation snapshot (up to the 8 most recent messages), displays recent sessions and lets you delete them. History may be unavailable until the migration is applied; a successful AI answer does not guarantee history was saved.

5. Home — AI prompt launcher#

1. Open [Home](/).
2. Enter your prompt in the main AI input or select a starter suggestion.
3. Choose Start with AI. CPU opens the Free AI page and pre-fills your draft.
4. Sign in if necessary, review the draft and click Send message.

Home is an entry point, not a separate model. It does not use your quota just by entering text.

6. Developer Dashboard#

1. Open Dashboard ↗.
2. Sign in through Free AI if your account is not yet active.
3. Check the daily quota and verified account status.
4. Use the shortcut tiles to open the right tool for your task.
5. Use Recent conversations to resume a chat, when conversation history is configured.
6. Check the Local workspace panel for browser-saved project files and agent profiles.

Workspace files and agent templates are counted on this device only; they do not automatically sync to your Google account.

7. Project Workspace — multiple source files#

1. Open Project Workspace ↗.
2. Enter your project name.
3. Use Add file to create a file, or Import files to load existing text/source files.
4. Select a file in the left list, then edit its contents in the code editor.
5. Use Save locally to store the project in your browser; Load saved restores that browser copy.
6. Use Export JSON to download a portable project snapshot.
7. Choose Copy code to copy the selected file, or Copy AI review prompt to prepare a short code review prompt.
8. Paste the prompt into Free AI Chat when you want an AI review. Copying the prompt does not itself call AI.

Limits: maximum 12 files per project; 15 KB per file. Save locally and export backups frequently. This editor does not execute, test, build or deploy source code.

Cloud Project Sync (optional)

1. Sign in through Free AI Chat, then open Project Workspace.
2. Prepare your source files. Click Save new cloud copy to explicitly upload this project to Cloudflare D1 under your Google account.
3. On another device, sign in with the same Google account, select Refresh list and click Open for your project.
4. Edit files and click Save changes. Version protection blocks overwrites if another device saved a newer version.
5. Click Delete to remove a cloud copy. Browser-local copies and downloaded JSON backups are not deleted.

Cloud limits: Up to 8 projects/account; 12 files and 15 KB per file. Cloud saving is optional and not end-to-end encrypted — never upload private keys or confidential code. It requires the migrations/0002_cloud_projects.sql D1 migration.

8. Repository Analyzer — inspect a public repository#

1. Open Repository Analyzer ↗.
2. Enter a public GitHub repository in the form owner/repo (for example cloudflare/workers-sdk).
3. Click Explore. CPU reads the repository tree through GitHub's public API.
4. Filter the displayed paths and select a supported source file.
5. Read the file preview and choose Scan code for transparent heuristic findings.
6. Use Export report to download the results for manual review.

Limits: up to 300 eligible source files are listed; files larger than 200 KB are skipped. GitHub may rate-limit requests. Private repositories cannot be read by this public, unauthenticated feature. Scanning is rule-based and is neither a comprehensive audit nor an AI review. No GitHub write operations occur.

9. Code Inspector — quick JS/TS checks#

1. Open Code Inspector ↗ on the Home page.
2. Paste a small JavaScript or TypeScript snippet into the input area.
3. Click Review snippet.
4. Review the flagged line numbers, risk categories and remediation suggestions.
5. Click Clear to remove the snippet from the current input.

The inspector searches for selected patterns such as dynamic evaluation, hardcoded credentials, unsafe HTML assignment and insecure URLs. It runs locally in your browser and is not a replacement for a security audit; false positives and missed issues are possible.

10. Patch Review — compare before and after#

1. Open Patch Review ↗.
2. Paste the Original code in the first box.
3. Paste the Proposed code in the second box.
4. Click Compare changes to see changes at corresponding line positions.
5. Use Export comparison to download the review.
6. Independently run tests and apply approved changes in your own editor.

Limit: up to 1,500 lines per version. This is a simple line-position comparison, not a complete unified diff algorithm, patch application engine or Git commit workflow. Inserted lines may shift later positions.

11. Agent Studio — define reusable agents#

1. Open Agent Studio ↗.
2. Select a template: Developer, Security Reviewer, Debugger, Architect or Custom.
3. Set the agent name, provider preset and model identifier.
4. Edit the instructions to describe goals, inputs, permissions and required output.
5. Click Generate profile to preview Markdown instructions.
6. Choose Save locally to store a template in this browser or Download .md to export it.
7. Load a saved template when you want to reuse or adjust it.

Important: Choosing OpenAI, Gemini, Ollama or any other provider in Agent Studio does not connect to that provider. This feature produces a reusable configuration document and does not run an agent.

12. Workflow Builder — plan a multi-agent process#

1. Open Multi-Agent Workflow Builder ↗.
2. Describe the project goal in plain language.
3. Choose a technology stack (such as Cloudflare Workers, React or Python).
4. Click Build workflow.
5. Review the handoff plan: Architect → Developer → Security Reviewer → Debugger/QA → Human Approval.
6. Use Download workflow to keep the planning document.

This is a structured, browser-generated plan, not a live conversation between collaborating AI agents.

13. Public GitHub Issue Explorer#

1. On Home, find Open-source issue explorer.
2. Enter a public repository name such as cloudflare/workers-sdk.
3. Click Load open issues.
4. Select an issue to view it on GitHub.

The tool is read-only and uses GitHub's public REST API; it does not create issues or make pull requests.

14. Model settings and Operator AI Chat#

The Models area lists potential AI providers and local runtimes. These are configuration presets, not proof that every listed model is available to CPU Free AI.

Free AI: Google sign-in, CPU backend and Cloudflare Workers AI; users do not enter AI API keys.

Operator AI Chat: Operator AI ↗ is a separate restricted experiment requiring an operator access code and configured server-side OpenAI API key. It is not the free public chat and should not be offered to untrusted users without per-user authentication, rate limiting and cost controls.

15. CPU AI architecture and data#

• Frontend: Cloudflare Worker static assets; English interface, responsive Light/Dark Mode, HTML/CSS/JavaScript.
• Identity: Google Identity Services sign-in; the backend verifies Google ID tokens and issues a CPU session cookie.
• Inference: Free AI uses a Cloudflare Workers AI binding (currently Llama 3.1 8B in the repository); the model can change as the service evolves.
• Database: Cloudflare D1 stores account details and daily quotas, plus saved conversation snapshots if that table was deployed.
• Local browser storage: Local Workspace copies, agent templates and appearance preferences. Optional cloud copies exist only when explicitly saved into D1.
• GitHub: public read-only API queries for code inspection and issues.
• No autonomous execution: the current website cannot install dependencies, edit private GitHub repositories, run code in a sandbox or deploy changes automatically.

Privacy and safety: Do not paste private keys, passwords or other sensitive information into chat. Submitted messages are processed by the AI provider; saved histories may be retained in CPU D1. Delete saved conversations through the UI where supported. Review all generated code before use.

16. Roadmap — staged, not promised dates#

The phases below describe development direction rather than committed release dates.

Phase 1 — Foundation (implemented in the repository)

Responsive interface, Light/Dark Mode, Google Login, free Workers AI chat, quotas, personal dashboard, basic code tools and project/agent templates.

Phase 2 — Product usability (implemented in code / needs production validation)

Better AI workspace interface, account-scoped history after D1 migration, code file attachments, quick review prompts, consistent Docs and easier navigation.

Phase 3 — Connected development (planned)

Optional Google-account Cloud Project Sync is implemented in code (requires migration); secure GitHub access, accurate diffs, test tools and pull-request creation remain planned.

Phase 4 — Agent execution (planned)

Isolated execution sandbox, scoped terminal/file permissions, multi-agent orchestration, audit logs, limits and developer approval before mutations.

Phase 5 — Community and optional token utility (research / proposal)

Community contribution system, transparent bounties, optional token-based participation and governance mechanisms where technically, legally and economically feasible.

Release criteria: security testing, billing/abuse controls, privacy disclosures and production validation matter more than fixed launch dates.

17. $CPU — proposed token concept#

Ticker: $CPU (proposed) Status: Concept / not launched or verified in this project documentation Blockchain/network: Not confirmed for this project Official contract address: Not announced Total supply, decimals, fee/tax, liquidity, allocation and launch date: Not specified Current token requirement: None — Free AI currently uses Google sign-in, not token holdings.

CPU AI may explore a token as an optional ecosystem utility, not as a prerequisite for basic access.

Proposed utilities (not active)

1. Optional advanced compute credits: Redeem $CPU for clearly priced extra AI analyses or advanced workflows if a metered backend and transparent pricing are implemented. This would not imply unlimited compute or free third-party infrastructure.
2. Agent ecosystem: Potential payments for optional agent templates, tools or marketplace services where creators opt in.
3. Community governance: Potential participation in defined roadmap or community decisions, with on-chain verification only after governance rules and contracts exist.
4. Developer bounties: Potential funding or recognition for verifiable code contributions, subject to review, anti-abuse rules and a real treasury.
5. Feature access: Optional access to premium experimental modules, while preserving an independently defined free user tier.

Token policy and transparency

• No claim of a deployed token, sale, airdrop, staking pool, guaranteed price, dividend, creator-fee revenue sharing or investment return is made here.
• Holding $CPU does not presently increase your AI quota, unlock private GitHub tools or confer governance rights.
• Token utilities, if introduced, will require specific implementation milestones, published tokenomics, security review and applicable legal/compliance assessment.
• Never send funds to an unverified “CPU” contract. Only use official links after an address has been publicly confirmed and independently verified.
• Product functionality will be tracked separately from token marketing.

18. FAQ#

Is CPU AI free? The present Google-linked Free AI tier provides up to 5 messages per account each UTC day, subject to provider capacity. Other public browser utilities generally require no AI credits.

Do I need an OpenAI or Gemini API key? Not for Google Free AI. Google sign-in handles account identity; CPU provides access to its configured AI backend.

Does CPU execute code or change my repository? No. Existing browser tools prepare, inspect or compare content. Any autonomous execution or write-back feature is future work.

Can CPU read my private GitHub repository? Not through the current public Repository Analyzer. It is limited to public data.

Are my project files saved on the server? Local Save writes to your browser. Opt-in cloud saves create separate project copies in D1 under your Google account; they can be deleted from Workspace.

Why did chat history disappear? A cleared browser session, missing D1 history migration, unsaved conversation, or different account may explain it. CPU should show a warning when history cannot be saved.

Is $CPU required to use Free AI? No. The token is only a proposed optional ecosystem component at this stage.

Where can I report a problem? Email support@cpuai.site for product support or privacy requests. The address receives messages through Cloudflare Email Routing.

Product notice: Documentation reflects repository features and the operator's reported functioning Google Login/AI Chat as of October 22, 2026. Production rollout and availability can differ by deployment. Roadmap and token ideas may change. This document is product information, not financial or legal advice.