Search42 Results

This article explains how to reduce token usage in Claude so you work efficiently and stay within your usage limits or budget. It covers managing the conversation, writing efficient prompts, handling files, and choosing a lighter model.

This article explains what to do if you have a personal Claude account on your @bowdoin.edu email and are not receiving access to Bowdoin's Claude Enterprise account. It covers how to create a new account on a personal email, export your conversations and skills, cancel a paid subscription, and what happens when the domain claim takes effect.

This article explains how your Claude working folder is backed up to OneDrive at Bowdoin. Because Bowdoin turns on OneDrive folder backup (Known Folder Move), the Documents folder syncs to OneDrive automatically, so a Claude Projects folder kept in Documents is backed up and available on other devices. It covers confirming folder backup, keeping files on your device, and the fact that Claude on the web cannot reach OneDrive directly.

This article gives folder and file best practices for working with Claude Cowork and Claude Code on a Bowdoin-managed account. It recommends a single dedicated working folder kept in your Documents folder, which syncs to OneDrive through Known Folder Move for automatic cloud backup and cross-device access, plus a simple per-project layout, clear file names, and what not to place in a folder you connect to Claude.

This article explains how to install Claude Code, open it in the right folder on your computer, and give it a first task, on a Bowdoin-managed account. It is written for non-technical readers and covers the working directory, the trust prompt, and how to exit, on macOS and Windows 11.

This article walks through setting up a project in Claude Cowork and connecting a folder on your computer so Claude can work with your files. It covers installing the Claude Desktop app, creating a project, connecting a folder on macOS and Windows 11, and disconnecting a folder when you are done.

This article describes how Projects, Cowork, and Claude Code work on a Bowdoin-managed Claude account, including what migrates from a personal account and what stays local. It also notes that publishing artifacts and public share links are not available on Team and Enterprise plans.

This article explains how data is handled in a Bowdoin-managed Claude account, including that prompts and outputs are not used to train models by default, that Bowdoin's Primary Owner manages the account and its data, and how retention works. It directs Bowdoin-specific policy questions to Bowdoin IT.

This article explains why a Claude Pro or Max subscription purchased through the Apple App Store is not canceled automatically during migration and how to cancel it in Apple ID settings to avoid being double-billed. It then covers starting the migration to the Bowdoin account.

This article explains why connected apps stop working after migration — authorizations are revoked for security — and how to reconnect them from the Bowdoin account. It also covers custom connectors, project sync re-authorization, and Bowdoin connector policy.

This article explains that custom skills have no migration path and are lost when a personal account closes, so they must be exported first. It walks through saving skills before migrating and re-adding them in the Bowdoin account, subject to College policy.

This article describes exactly what moves and what does not move when you migrate a personal Claude account into Bowdoin's managed workspace, including chats, projects, skills, and connectors. It also explains what happens to a paid Pro or Max subscription depending on how it was purchased, including the Apple App Store case.

This article helps Bowdoin community members decide what to do with a personal Claude account when they join Bowdoin's managed Claude organization. It compares keeping both accounts with switching to the Bowdoin account, explains how to make and change the choice, and recommends using the Bowdoin account for College work.

This article explains how to get access to Claude at Bowdoin through a three-tier model: LibreChat for everyone, the Claude tools by request, and application programming interface access through Portkey (coming soon). It also lists what the access request will ask for.

This article explains how to choose the right Claude model for a task. It compares the Haiku, Sonnet, Opus, and Fable models, gives guidance by task type, and shows how to change the model in the Claude apps.