Projects

OCI Generative AI projects organize conversations, responses, files, and sandboxes under shared settings. Configure data retention, memory, and the networking used by sandboxes in the project.

Projects are isolated from each other to support lifecycle management and compliance boundaries. Reference the project OCID in API and SDK calls to apply project settings at runtime.

About Projects

A project is an OCI resource that organizes agent-specific artifacts created through the Generative AI service, including responses, conversations, files, containers, and sandboxes. Projects are isolated from each other, so artifacts in one project aren’t accessible from another project. A project is required to call the OCI OpenAI-compatible API for agent-related tasks.

A project setting can include:

  • Data retention for responses and conversations
  • Long-term memory settings
  • Conversation history compaction (short-term memory compaction) settings
  • Sandbox enablement and outbound networking settings
  • Warm pools that prepare capacity for new sandbox requests
  • Deleting a project deletes all associated artifacts (responses, conversations, files, and containers) created within that project.
  • API calls use the Project OCID.

Sandboxes and Warm Pools

Enable sandboxes in a project to run code and shell commands in temporary, isolated workspaces. You can create multiple sandboxes in the project and address each sandbox by its ID. See Sandboxes in OCI Generative AI.

Sandboxes in a project share the project's outbound networking configuration and the OCI permissions granted to sandboxes from that project. Use separate projects or appropriately scoped policies for workloads that need different access.

Warm pools prepare idle capacity for new sandbox requests. You can configure pools when creating a project and view them on the project's Warm pools tab. See Warm Pools for Sandboxes.

Response and conversation retention settings apply to those artifacts. Sandbox expiration and snapshot retention are configured separately. See Sandbox Runtimes and Resource Limits.

Agent Memory

Agent Memory enables agents to retain and use context across interactions. It supports both short-term memory within a conversation and long-term memory across conversations, helping improve continuity, relevance, and efficiency.

Short-Term Memory

Short-term memory refers to the conversation context carried forward within an ongoing conversation. The Responses API and Conversations API simplify conversation state management, enabling multi-turn interactions.

Long-Term Memory

Long-term memory provides persistent context across conversations. When enabled, the service extracts key information from conversations and stores it so it can be recalled in future interactions within the same project.

Long-term memory is useful for scenarios that require continuity across sessions, such as:

  • Remembering stable user preferences
  • Retaining recurring background context
  • Maintaining continuity across interactions

Short-Term Memory Compaction

As conversation history grows, sending the full history can increase token usage and latency. Short-term memory compaction summarizes and compresses earlier conversation history into a smaller, structured representation. This helps preserve key details while reducing the amount of context sent to the model.

This approach:

  • Preserves key information from earlier turns
  • Reduces token usage for long conversations
  • Improves latency by keeping context lightweight

Data Retention

Data retention defines how long project artifacts are kept before they’re automatically removed. In OCI Generative AI projects, you set retention separately for responses and conversations.

  • Response retention: Controls how long generated responses are retained.
  • Conversation retention: Controls how long conversations are retained after the most recent update.

Retention settings help you control storage duration and align with your organization’s data handling requirements.

QuickStart Permissions

  1. Add the minimal IAM policy needed to get a project OCID.
    allow group <your-group-name> to use generative-ai-project 
    in compartment <your-compartment>
  2. (Optional) Instead of the previous permission, if you need to create and delete projects, add the following policy:
    allow group <your-group-name> to manage generative-ai-project 
    in compartment <your-compartment>

    For guidance, see IAM Policies for OCI Generative AI.