Projects

A project in C3 represents a directory on your development machine. When you create a project, you're telling C3 where your AI coding agent should operate.

Creating Projects

There are two ways to create a project in C3:

Option 1: Point to an Existing Directory

Create a project from a folder that already exists on your machine:

Name — A friendly name you choose (e.g., "My Web App")
Description — Optional notes about the project
Directory Path — The absolute path on your computer, or tap the folder icon to browse and select a directory

Browse for Directory

Instead of typing the full path, tap the folder icon next to the directory input field to open a file browser. Navigate to your project folder and select it — the path will be filled in automatically.

Text

# Example project paths
/Users/you/projects/my-app          # macOS/Linux
C:\Users\you\projects\my-app       # Windows

Option 2: Clone from GitHub

Clone a repository directly from GitHub and create a project for it:

Tap the + button on the Projects screen
Select Clone from GitHub
Search or browse your repositories (personal and organizations)
Select a repository
Choose a branch to clone
Specify the target directory (defaults to your home folder)
Tap Clone to clone the repository

After cloning, a project is automatically created pointing to the cloned directory.

GitHub CLI Required

Cloning from GitHub requires the GitHub CLI (gh) to be installed and authenticated on your development machine. See the Git Integration page for setup instructions.

Path Tips

Always use absolute paths. Relative paths like ./my-project won't work because C3 doesn't know your current directory context.

Project Context

When you open a project in C3, your AI agent runs with that directory as its working directory. This means:

File paths in the agent's responses are relative to the project root
The agent can read your configuration files
Git operations work on the project's repository
Terminal commands execute in the project directory

Sessions

A session is a single conversation with your AI agent within a project. Each session maintains its own conversation history, context, and state.

Session Properties

Property	Description
Session ID	Unique identifier for the session
Title	Auto-generated or custom session name
Created	When the session started
Model	The AI model being used
Permission Mode	How tool approvals are handled
Context Usage	Token consumption statistics

Session Storage

Sessions are stored securely on your machine and synced with the app as needed. For Claude Code, C3 uses the same storage format, so your sessions are accessible from both the mobile app and the desktop CLI.

Session Management

Starting a Session

When you open a project and send your first message, C3 starts a new session. You can also explicitly create a new session from the project view.

Resuming Sessions

C3 can resume existing sessions, picking up where you left off. There are two ways to resume a session:

From the Project Card

Tap the Resume button on the project card to continue your most recent session
Tap the info icon (ⓘ) next to the Resume button to see a list of all sessions
Select any session from the list to resume it

From the Chat Screen

Tap the plus icon (+) in the chat screen to open the session modal
Browse through your previous sessions and select one to resume

When you resume a session:

Your conversation history is restored automatically
The agent remembers the context from your previous discussion
You can continue the conversation seamlessly

Context Continuity

When resuming a session, the agent remembers the conversation history and any context about your project it learned during the session.

Checkpoints & Rewind

Sessions automatically create checkpoints at key moments. You can rewind to any checkpoint to:

Undo Code Changes — Revert files to their state at that point
Restart Conversation — Go back to an earlier point in the chat
Both — Reset both code and conversation together

Context Window

Each session tracks token usage in the context window. C3 shows you:

Total tokens used vs. available
Breakdown by category (system prompt, tools, messages)
Visual indicator when approaching the limit

When the context window fills up, the agent can automatically compact older messages to make room for new ones — if you have auto-compact enabled in your agent's settings.

Multiple Sessions

You can have multiple active sessions within a project. This is useful for:

Parallel Tasks — Work on different features simultaneously
Experimentation — Try different approaches without affecting main work
Review — Keep a session for code review while coding in another

Session Limits

C3 limits concurrent active sessions to conserve resources (default: 10). Inactive sessions are automatically paused after 30 minutes and can be resumed when needed.

Worktrees (Advanced)

For Git-based workflows, C3 can use Git worktrees to give each session its own isolated branch. This prevents file conflicts when multiple sessions are making changes simultaneously.

When to Use Worktrees

Enable worktrees when you want to work on multiple features in parallel without commits interfering with each other. Each session gets its own working directory and branch.

Switching Sessions

Switch between sessions using the session list in your project view. The currently active session is highlighted, and you can see at a glance:

Session title and total session messages
Time since last activity
Current status (active, idle, processing)