Feature availability and providers
Distinguish local provider access from cloud, browser, desktop and workspace capabilities.
Identify where a task runs: local CLI/app/IDE use local configuration; hosted cloud, Slack, Linear and GitHub review use managed environments; browser and computer tools have separate device permissions.
Configuring Passion8 changes model routing for supported local workflows. It does not grant official cloud tasks, connectors, browser extensions, computer control or workspace administration.
#Capability overview
| Capability | Local Passion8 provider | Official account/API | Key check |
|---|---|---|---|
| Local CLI coding | Supported route required | Subject to account access | Configuration and working-directory permissions |
| Desktop local project | Client/provider compatibility required | Subject to client access | Same runtime configuration |
| IDE extension | Client/provider compatibility required | Subject to extension access | Runtime user and configuration |
| MCP | Separate local/tool setup | Separate tool setup | Server and tool permissions |
| Skills/plugins | Local skills; connected capabilities vary | Account/workspace-dependent | Local package versus cloud connector |
| Cloud/Web tasks | Does not inherit local Passion8 | Official hosted access | Repository/environment connection |
| Slack/Linear | Does not inherit local Passion8 | Official connector access | Hosted task creation |
| GitHub review | Does not inherit local Passion8 | Official review access | Repository and workspace permissions |
| Chrome extension | Not a model-provider entitlement | Requires extension/browser access | User profile and permissions |
| Computer Use | Not a model-provider entitlement | Requires device/app access | Allowed desktop applications |
| Fast mode | Model catalog and route-dependent | Account/catalog-dependent | API credentials are not ChatGPT credits |
#Local capabilities
Local workflows include CLI, IDE, local app projects, MCP, AGENTS.md, skills, hooks, rules, sandbox and approvals. Inspect three layers:
| Layer | Question | Location |
|---|---|---|
| Provider | Where do model requests go? | config.toml |
| Credentials | Which key or account is used? | auth.json, credential store or environment |
| Permissions | What files, commands and network access are allowed? | Sandbox, approvals, rules and hooks |
For Passion8 model routing, start locally and verify base_url = "https://passion8.cc/v1".
#Hosted capabilities
Cloud tasks, hosted reviews and official connectors use their own repository/environment configuration and return results such as diffs, PRs or task links.
| Entry point | Code/context | Provider boundary |
|---|---|---|
| Web/cloud | Connected repository and environment | Does not read your laptop's config.toml |
| GitHub review | PR diff and repository settings | Runs through the hosted integration |
| Slack/Linear | Connector context and repository environment | Creates tasks through official services |
Cloud environments can define setup scripts, variables, secrets and agent network access. Check current environment policy for which phases receive secrets and network access; do not assume local permissions apply.
#App, browser and computer tools
| Capability | Purpose | Important distinction |
|---|---|---|
| In-app browser | Preview pages inside the app | Separate from your normal browser profile |
| Browser use | Interact with that browser | Useful for local development and public pages |
| Chrome extension | Use your Chrome profile | Signed-in state and page content may enter task context |
| Computer Use | Control permitted desktop applications | Local file/shell permissions still apply |
These require the relevant app, plugin, OS/browser authorization and workspace policy. Changing base_url does not enable them.
#Verify Passion8 routing
| Question | Verification |
|---|---|
| Did this request use Passion8? | Match console usage with active provider, model, time and request diagnostics |
| Does cloud use Passion8? | Do not assume local configuration is synchronized |
| Does the IDE use Passion8? | Verify CLI, restart IDE and inspect its runtime configuration |
| Does the app use Passion8? | Start a local thread and correlate provider/model with console usage |
| Is a plugin available? | Distinguish local packages, MCP servers and official account connectors |
#Common misconceptions
| Misconception | Correct interpretation |
|---|---|
| Local Passion8 setup also configures cloud | Cloud has a separate execution environment |
| API-key sign-in equals ChatGPT sign-in | API keys, account sessions and access tokens differ |
| A visible MCP tool may write anything | Tool authorization and approval boundaries still apply |
| Chrome extension equals in-app browser | The former can use your profile; the latter is a separate browser |
| Full access only removes prompts | It also broadens execution and data-access risk |
#Recommended starting points
| Goal | Entry point |
|---|---|
| First Passion8 setup | Verify CLI before app/IDE |
| Private local project | Local workflow with read-only or workspace-write |
| Background tasks | Local automation or cloud, chosen by routing requirements |
| PR review | Local /review for local provider; hosted review for official integration |
| Browser debugging | Select browser tooling based on login-state needs |
| Enterprise governance | Workspace policies plus local managed configuration and gateway policy |
#Official references
Support
Need help?
For setup, billing, or model issues, email us. Check the status page for uptime.
WeChat / QQ support is available at the bottom right.
