Skip to main content
Projects keep related research in one place. Each project contains tasks and project-scoped files; it can also provide context, instructions, and default Skills to every new task.

​
Quick Tasks and named projects

Quick Tasks is the default project for one-off work. It behaves like a normal project, including file sharing between its tasks. Create a named project when work has a durable research question, dataset, or team. Open the project selector in the sidebar and choose Create a new project.

​
Tasks

A task is one conversation with Biomni. Within a project, each task has its own:
  • message and execution history;
  • generated results;
  • plan, compute activity, and notes; and
  • model profile.
The project sidebar shows its tasks and current activity. Use separate tasks for analyses with different goals or assumptions; keep follow-up refinement in the same task.

​
Project files and Results

Uploaded and imported files belong to a project. Biomni can use project files in that project’s tasks, and you can select an existing file from + Add without uploading it again. Generated task output appears in Results and remains associated with the project. Depending on the file type, you can preview, download, rename, move, or delete it. Internal execution artifacts are hidden from normal file views.
Access follows the project. A file from another project must be copied, imported, or explicitly selected through an available product flow before the current task can use it.

​
Drive

Drive is the project-level file browser. Use it to:
  • browse folders, uploads, and generated files;
  • upload files or folders;
  • preview and download supported formats;
  • rename, move, or delete content when your role permits; and
  • inspect project file activity.
Cloud imports copy external files into project storage. See Cloud Storage for supported import flows.

​
Project settings

Open Settings → Projects and select a project.

​
Project context

Describe durable facts Biomni should know in every new task, such as the study, organism, assay, cohort, or dataset conventions.

​
Custom instructions

Set project-specific response or workflow requirements. These are more specific than personal instructions but cannot override safety controls.

​
Auto attached Skills

Choose Skills that should be attached to the first message of every new task. Keep this list short and limited to workflows the project genuinely uses by default.
Project settings are captured when a task is created. Editing them affects new tasks; existing tasks keep the context, instructions, and Skill versions they started with.

​
Collaboration

Team workspaces can share a project as Viewer, Editor, or Admin. Project tasks and files inherit that access, with additional creator-only rules for steering a task and editing its notes. See Collaboration for the complete role model.