Plans Sign In Register
DMJBot - Personal AI Assistant

Projects

Wiki

Projects

A project groups related chats together and gives that group its own workspace: its own instructions, its own set of tools and skills, and a shared folder of files. Anything you do outside a project lives in the common context — the default, project-less area.

Why projects are useful

When you use one assistant for everything — work, side projects, personal errands — it is easy for things to get tangled: the wrong tool fires in the wrong chat, files from one effort mix with another, and you end up re-explaining context every time you switch topics.

Projects fix that by keeping each stream of work separate:

  • Less confusion. Each project has its own chats and its own files, so unrelated work never mixes.
  • The right tools in the right place. You decide which tools, devices and skills are available inside a project — and which stay out of it.
  • Set the context once. Give a project its own instructions (tone, role, rules) and every chat in that project follows them automatically.
  • Shared files. Every chat in a project can see the project's files, so you can pick up where another chat left off.
  • Safer. A tool or device you only need for one project doesn't have to be exposed everywhere.

A typical setup might be one project per client, per product, or per area of your life — for example "Acme Website", "Personal", and "Reading list" — while quick one-off questions stay in the common context.

What lives in a project

  • Chats. A chat belongs to a project or to the common context. Inside a project you see only that project's recent chats.
  • Project instructions. Optional instructions used for every chat in the project, in place of your general assistant instructions.
  • Shared files. All files in a project are available to every chat in it. (In the common context, a file is only visible to the chat that created it.)
  • Available tools, devices, skills and quick buttons — controlled by the scope rules below.

Controlling what each project can use

For every tool server, device, skill and quick button you choose where it is available using three simple switches:

  • Common — available in the common context (chats outside any project).
  • All projects — available in every project.
  • Selected projects — available only in the projects you tick.

A few things worth knowing:

  • Nothing is ever turned off everywhere. If you untick all the options, it stays available in the common context.
  • New things start private to the common context. A server, device, skill or button you just added is only available in common until you grant it to a project.
  • Granting a device shares its tools. When you give a project access to a connected device, all the tools (MCP servers) running on that device become available in that project.
  • Skills and quick buttons follow the same rules. A skill or a personal quick button only appears in a project when it is scoped to that project. Built-in skills are always available everywhere.

Where to manage projects

  • Settings → Projects — create or delete projects, and use the access grid to choose which projects (and the common context) may use each tool server, device, skill and quick button.
  • A project's own settings — set its title, its instructions, and its available tools, devices and skills.
  • Settings → Quick Buttons — each button has a "Visible in" choice so you can scope your shortcuts to specific projects too.

New tools and devices are still added from the usual Tools and Devices settings. The Projects page is where you decide which projects may use them.

Tasks and assignments

Background tasks and assignments belong to the project of the chat that started them (or to the common context). When you are inside a project you see that project's tasks and assignments, and the Tasks and Assignments pages let you filter by project.

See also