Ark: manage projects, sessions and running apps from one workspace

Build the project list from existing work

The 13 April 2026 description presents Ark as Luke’s local command centre for multiple Claude Code terminals. It scans folders and existing chats to assemble a project list, then brings projects, sessions and running apps into a browser interface. The examples span SaaS, client sites, email work and a portfolio; use this organisation to distinguish unrelated projects and keep each session’s working files clear.

1. Use the retained product resource: https://getark.app.
2. Follow the document scan at 1:10 and inspect which projects and sessions have been associated.
3. Open one known project and confirm that the crew member represents the intended Claude Code session before assigning a task.

Resume the right chat and inspect the actual output

History-based continuation appears at 2:30, HTML previews at 3:19 and full localhost apps at 4:07. Opening a preview and resuming a chat serve different purposes. The first reveals the current output; the second continues a conversation whose decisions may need to be checked against the project’s present files.

1. Select the relevant history entry and identify what is complete and what remains before continuing.
2. Preview the HTML artifact and compare its contents with the request that produced it.
3. Open the running app in full mode and complete the relevant user journey rather than judging the dashboard thumbnail.
4. Check that any repair appears in the version you are actually testing.

Review generated next tasks and access claims

The final sequence covers workflows and Scan Chats at 6:01. Treat generated next tasks as suggestions to compare with current work, not proof that an old request is still needed. The source promotes real terminals, no API keys and “no limits”; terminal-based access does not independently establish unlimited model usage.

1. Review suggested tasks for duplication, stale context and overlap before starting them.
2. Inspect the licensing route described at 5:34 through https://www.skool.com/luke before relying on the recorded free-access offer.
3. Keep each crew member’s task and output identifiable when several sessions are running together.

The takeaway

A command centre earns its place when you can find the right session, inspect its real output and continue only the work still needed.