Creating a task
You can create a task and work agentically from the browser in Cloud.
Tasks overview
Section titled “Tasks overview”
Here you can create a new task or open a previous task.
Task input field
Section titled “Task input field”You can get started by adding a task to the input field straight away. You can also adjust the task settings before you launch it.
Agent Mode
Section titled “Agent Mode”
When creating a task you can choose between:
- Manual for a straightforward single-agent workflow
- Plan when you want Cosine to research the task, inspect the codebase, and propose an approach without making changes yet
- Swarm when you want multiple agents to split up the work
- Auto when you want Cosine to switch between approaches automatically as the task develops
These modes are essential because they shape how much autonomy the agent has and how it breaks down the work.
See Models and Pricing for a dedicated overview of the available modes.
Repository
Section titled “Repository”Choose the GitHub repository Cosine should work in.

Every task runs against a specific imported repository. Pick the repository that contains the code, docs, or configuration you want the agent to work on.
If you have several repositories connected to the same team, make sure you select the one that actually owns the change. This keeps the agent grounded in the right codebase from the start.
Choose the model that fits the complexity and cost profile of the task.

For smaller or well-scoped tasks, a lighter model may be enough. For more ambiguous, research-heavy, or multi-step work, a stronger model can be a better fit.
See Models and Pricing for the current model catalog and pricing multipliers.
Environment
Section titled “Environment”Choose the environment where the task should run.

The environment determines the workspace the agent will use while carrying out the task. It controls what tools, languages, and dependencies are available.
Base environments like Ubuntu, Browser, Desktop, VS Code, and Slim work immediately without setup. Custom environments created in your project settings provide project-specific tooling and dependencies.
See Environments for more detail on available environments and how to create custom ones.
GitHub branching
Section titled “GitHub branching”Choose the base branch and the working branch for the task.

This is where you define:
- the base branch the task should start from
- the branch name the agent should use for its work
This is useful when you want the task to target a release branch, a staging branch, or a clearly named feature branch instead of relying on a default.
See also
Section titled “See also”- [Overview](/cloud/)
- Quickstart
- Agent modes
- Models and Pricing
- Environments