Projects and sessions
Keep durable organization around the provider work that already belongs to a project and machine.
Projects and locations
A Project is the durable workspace identity. Its authorized folder is a machine-specific Project Location. Registering a folder never gives CodeTether permission to delete that folder.
Create and organize conversations
- Each conversation keeps one immutable machine, project, and provider.
- Rename, pin, archive, and unarchive without starting the provider.
- Search project-scoped titles and user inputs, then jump to the matching turn.
- Archived history stays readable, but must be restored before new work starts.
Review attention, output, and changes
The conversation timeline keeps normalized agent messages, supported tool activity, files, diffs, and approvals in context. The Inbox highlights work that needs a decision or review.
Continue provider-native sessions
- Discover bounded session metadata for the selected provider and authorized project location.
- Adopt the native session as one CodeTether conversation reference without copying provider credentials.
- Open the conversation and explicitly resume through the provider-native mechanism when you send new work.
Continuity limits
CodeTether does not move a conversation to another provider or machine, replay historical prompts into a new session, or promise recovery when a provider no longer exposes the original native session.
CodeTether never treats a lost network response as permission to replay provider work automatically. When execution ownership is uncertain, inspect the conversation before starting a fresh task.