How to Use Claude on Your Phone for Ongoing Work

The Claude mobile app is available on iOS and Android and covers most of what the web version does: text conversations, file and image uploads, Projects with shared instructions, and voice dictation through your keyboard. For focused tasks — drafting, reviewing, researching — the phone app is a capable option away from your desk.

For ongoing work, the main challenge is context. A Claude conversation does not carry its content into the next one, so each new session starts from scratch unless you bring that context with you. Tools like fenbs keep projects, tasks, and standing rules outside any one app, so a session that starts on your phone can continue what a desktop session left off without re-explaining the work.

What the Claude mobile app supports

The Claude mobile app gives you access to the main Claude features:

• Text conversations: ask questions, draft content, think through problems.
• File uploads: share PDFs, spreadsheets, and images from your camera roll or Files app.
• Projects: each Project holds its own system prompt and conversation history, synced across desktop and mobile.
• Voice input: use your keyboard's built-in microphone to dictate messages rather than type them.
• Multiple accounts: switch between personal and team accounts if your plan allows it.

Computer use and code execution environments are desktop-only features for now. For a hands-free voice workflow, see how to use Claude hands-free.

How to start ongoing work in the mobile app

1. Download the Claude app from the App Store or Google Play and sign in with the same account you use on the web.
2. Open or create a Project for your recurring work. Write a system prompt with the project's goal, the tone you want, and any rules that always apply.
3. Start a conversation inside the Project. The Project instructions are loaded automatically at the start of each conversation.
4. To share a document, tap the attachment icon and pick a file from your camera roll or Files app. Claude can read PDFs and common document types.
5. To speak rather than type, tap the microphone icon on your keyboard, dictate, review the transcription, then send.

The context gap between sessions

Claude Projects keep their instructions across every conversation, but the content of one conversation is not visible in the next unless you paste it in. If you spend time working through a plan in one session, the next session — on any device — starts with only the Project instructions and nothing from the previous chat.

This is not a phone-specific limitation. It applies on desktop too. The practical effect is that decisions, task progress, and next steps need a home outside the conversation if they are going to survive to the next session.

One way to test whether this matters for your work: start a second session on a task you worked through in a previous conversation, without copying anything over. If you can continue immediately, the essentials are already in the Project instructions. If you find yourself re-explaining the situation, the gap is real and worth addressing before it becomes a recurring pattern.

For a deeper look at how Claude handles project context, see what is Claude CoWork.

Keeping the project brief across devices

One option is to write a short project summary in the Project's system prompt and update it after each session. This works for personal projects where the work moves slowly. It gets harder when tasks multiply, decisions stack up, or other people need access to the same record.

A dedicated project tool makes the record easier to maintain. When Claude is connected to fenbs over MCP, the assistant can read the current project context — rules, Where we left off, and open tasks — at the start of each session. That context is available whether the session starts on a desktop or a phone browser.

How to do this with fenbs

1. Create a free account. Set up a project for the ongoing work you want available on mobile.
2. Add the project goal, current tasks, and any standing decisions to fenbs. Keep it focused on what the next session actually needs.
3. Connect Claude to fenbs from Integrations. Follow the MCP guide for Claude and approve only the access you intend to give.
4. At the start of each session, ask the assistant to read the project context: rules, Where we left off, and what is in progress.
5. Before ending the session, ask the assistant to save progress on the tasks it touched and update Where we left off. That gives the next session a current starting point.

fenbs has a phone app on the App Store and Google Play, and the web app works in a phone browser. You can check and update your projects and tasks from any device, including when you are not in a Claude session.

When the mobile app is not the right choice

The Claude mobile app is well suited for focused questions, quick reviews, and light drafting. For long coding sessions, multi-file work, or anything that benefits from a large screen, the desktop version is more practical. Browse the AI at work topic for more Claude workflows for ongoing projects.