Skip to main content
Book a demo

Connect Asana to Codex

Give Codex governed access to Asana’s 39 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Codex setup guide

Set up

Add Asana to Codex in four steps

Admins approve the server once. Everyone in Codex then gets it through the same governed connection.

  1. 1

    Approve Asana in Runlayer

    Add Asana from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Codex to Runlayer

    Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Asana’s 39 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).

    Codex setup guide
  3. 3

    Sign in to Asana

    Each user signs in to Asana with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Asana from Codex

    Asana’s approved tools appear in Codex. Every call is checked against policy and recorded.

Tools

39 Asana tools in Codex

Runlayer policy decides which of these Codex users can call.

  • Add comment

    Add a comment to a task.

  • Create project

    Create a new project with optional sections and tasks in a single operation.

  • Create project confirm

    DEPRECATED; DO NOT USE.

  • Create project confirm populate

    DEPRECATED; DO NOT USE.

  • Create project from template

    Create a project from a project template.

  • Create project preview v3

    Show a visual preview of a project structure before the project is created in Asana.

  • Create project status update

    Post a status update to a project or portfolio.

  • Create task confirm

    DEPRECATED; DO NOT USE.

See all 39 Asana tools

Control

What Runlayer can see and stop in Codex

Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.

  • Gateway policy (available)

    Every Asana call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before Codex runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Codex’s model sees it.

  • Redact output in place (not available)

    Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination