# Codex



<HostChip host="codex" />

Codex has full Knosy support, including sessions without a project.

## What you get [#what-you-get]

* **Launch with or without a project.** Start a session in a folder, or choose **No project** for work that doesn't belong to one.
* **Context on the first prompt.** With the integration connected and trusted, your first prompt waits for the scope you confirm and the first answer already has that context. See [The scope picker](/docs/concepts/scope-picker).
* **Live status.** Session cards follow the conversation: working, needs you, done.
* **Jump back.** Where Codex makes it possible, Knosy opens the exact conversation. Otherwise it focuses Codex and says so.

## The trust step [#the-trust-step]

Codex protects you by asking you to review and approve any new integration yourself, and Knosy never works around that.

<Steps>
  <Step>
    ### Connect in Knosy [#connect-in-knosy]

    Connect Codex during [first-run setup](/docs/getting-started/setup) or in **Settings → Integrations**. Knosy shows the integration as **trust pending**.
  </Step>

  <Step>
    ### Approve in Codex [#approve-in-codex]

    Open Codex's hooks review (the `/hooks` command) and approve the Knosy entry.
  </Step>

  <Step>
    ### Done [#done]

    Knosy verifies the connection and the status changes to connected. If Codex ever asks again after an update, Knosy shows **trust pending** once more and points you back to the review.
  </Step>
</Steps>

As with Claude Code, Knosy backs up your configuration before any change, adds only its own entries, and removes exactly those when you disconnect.