# Codex Platforms and integrations

> Codex: Local CLI, app, IDE, hosted services, remote connections and provider boundaries.

URL: https://docs.passion8.cc/en/docs/codex/platforms-integrations
Language: en
Publisher: Passion8

Codex has multiple local and hosted entry points. Local clients can read their runtime's Codex configuration; hosted integrations use their own account, workspace and environment settings.

## Choose an entry point

| Entry | Execution | Suitable work | Inherits local Passion8? |
| --- | --- | --- | --- |
| CLI | Local terminal | Coding, review and scripts | When configured in that runtime |
| Desktop Local | Local app | Threads, review, worktrees and device tools | When the client supports the selected provider |
| IDE | Editor runtime | Code-context collaboration | When using that runtime's configuration |
| Web/cloud | Hosted environment | Remote tasks and PRs | No automatic inheritance |
| Slack/Linear | Hosted tasks | Dispatch from collaboration tools | No automatic inheritance |
| GitHub review | Hosted integration | Team PR review | No automatic inheritance |
| Action/CI | Runner | Automated review/migration/checks | Depends on runner setup |
| Remote connections | Connected host | Control tasks from another device | Uses the host's configuration |
| Sites | Hosted publishing | Share websites and prototypes | Separate hosting/account capability |

## The local clients

CLI, supported local desktop workflows and IDE extensions can share configuration for the same runtime user:

| Setting | Location |
| --- | --- |
| Provider, model, sandbox | ~/.codex/config.toml |
| Credential/session | auth.json or configured credential store |
| Project rules | AGENTS.md |
| MCP | mcp_servers tables |
| Skills/plugins | Supported local installation directories |

Example environment-key provider:

```toml
[model_providers.passion8]
name = "Passion8"
base_url = "https://passion8.cc/v1"
env_key = "OPENAI_API_KEY"
wire_api = "responses"
```

Select it with the corresponding top-level model_provider and supply a Passion8 key in that environment variable. This is an alternative to the auth.json route, not an additional required login. Claude Code's endpoint convention differs; do not copy its URL format into Codex.

## Web and cloud

Use the current official web/cloud entry to connect a repository and configure an environment.

| Scenario | Benefit |
| --- | --- |
| Dispatch from mobile/web | Does not require the local terminal task to remain open |
| Several remote tasks | Isolated hosted environments |
| Prepare a PR | Repository integration |
| Team collaboration | Workspace permissions, audit and review |

Boundaries:

- Hosted execution does not read your laptop's config.toml.
- Repository connections and environments must be configured separately.
- Private dependencies, variables and secrets need environment setup.
- A local Passion8 provider does not automatically route hosted tasks.

## Slack and Linear

| Tool | Trigger | Prerequisites |
| --- | --- | --- |
| Slack | Mention @Codex in the supported context | Official integration and repository/environment access |
| Linear | Assign or mention Codex where supported | Connector and repository/environment access |

To read an issue from a local task, an MCP connection may be more appropriate:

```bash
codex mcp add linear --url https://mcp.linear.app/mcp
codex mcp login linear
```

The same distinction applies to Slack: reading through a local tool differs from creating an official hosted task.

## GitHub integration

| Path | Execution |
| --- | --- |
| Local Git/gh | Uses local tools and can use the configured Passion8 model |
| Hosted PR review | Official integration, such as @codex review |
| Codex Action | Runner setup and Action configuration determine routing |

A practical sequence:

1. Develop locally in CLI/IDE/app.
2. Run /review before the PR.
3. Use hosted or CI review for the team process.
4. Limit automatic fixes to trusted branches and scoped permissions.

## Remote connections

A remote connection uses the connected host's project, threads, files, credentials, MCP, plugins and relevant device-tool settings.

Suitable uses:

- Monitor a long task from another device.
- Send follow-up instructions to an office/development machine.
- Work in an SSH host's filesystem and shell.

Keep ordinary SSH and authentication controls. The host's sandbox, approval and browser/computer permissions still apply; remote access is not a bypass.

## Sites

Sites is a hosted publishing capability, separate from configuring your own server. Check current account and service availability before using it.

| Question | Approach |
| --- | --- |
| Local preview only? | Use a dev server and browser tool |
| Public/workspace sharing? | Consider a supported hosting workflow |
| Database or storage? | Identify the required persistence services |
| Secrets? | Use the host's runtime secret settings, not source files |

Treat published deployment URLs as live deployments. Verify audience, build, environment variables and migrations before publishing.

## Continue reading



- [Feature availability](https://docs.passion8.cc/en/docs/codex/feature-availability): Provider and account capability boundaries.
- [Browser and Computer Use](https://docs.passion8.cc/en/docs/codex/browser-computer-use): Browser profiles and device access.
- [Review workflows](https://docs.passion8.cc/en/docs/codex/review-github): Local, hosted and CI review.



## Official references

- [Codex manual: app, CLI and IDE](https://developers.openai.com/codex/codex-manual.md)
- [Codex manual: web, Slack and Linear](https://developers.openai.com/codex/codex-manual.md)
- [Codex manual: remote connections and Sites](https://developers.openai.com/codex/codex-manual.md)