How to build a journal app with Claude Code agents
u/CatalinMihaiSafta built a personal journal app through Claude Code sessions controlled from a phone. Separate engineer worktrees, a reviewing agent and a single active engineering seat reduced the conflicts they encountered with parallel work.
reddit.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
For [personal app], turn [requested change] into a scoped engineering task. Assign it to one isolated worktree, wait for its diff and test report, and review before starting the next task. Use [existing deployment script] as the deployment gate; do not bypass failed checks.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- u/CatalinMihaiSafta
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports two months of development on a personal journal app and provides a public demo with fictional journal data. Their deployment script caught most failed deployments in tests. They clarified that only one engineer works at a time, alongside the persistent reviewing session.
- Human involvement
- The author set project rules, gave requests from a phone and could reorder the work queue. A fixed script enforced tests and health checks rather than trusting an agent's success claim.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The author gave requests from a phone to a separate reviewing session called Number One.
- Engineer sessions worked in separate Git worktrees and branches with project rules in CLAUDE.md.
- A queue allowed only one engineer to work at a time while Number One reviewed its diff and report.
u/CatalinMihaiSafta describes building a Star Trek-styled personal journal app over two months while giving instructions from a phone. The account links a public demo populated with fictional journal entries. Its useful detail is how the author limits competing coding sessions.
Each engineer has a Claude Code session in a separate Git worktree. A persistent session called Number One turns short requests into orders, reviews diffs and reports, and controls deployment. Project instructions specify build rules, production locations and files the agents must not touch.
The title could suggest a large parallel team, but the author's comments clarify the arrangement. At most two Claude Code instances are open: Number One and one active engineer. Engineers wait in a work queue, and the reviewer sees a report before the next starts. The author abandoned broader parallel work because rebasing and conflict repair consumed more time and tokens.
Deployment also has a separate check. A fixed script rebases, runs tests, merges and restarts, then rolls back if health checks fail. The author reports failed deployments, mostly caught by tests, rather than claiming that the agents never break anything.
This is useful for solo developers who want agent-assisted maintenance without several simultaneous engineers competing for the same codebase.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Reddit · u/CatalinMihaiSafta
Frequently asked questions
How many engineer agents run at once?
The author clarified that only one engineer works at a time. A separate persistent Number One session reviews the work, so at most two Claude Code instances are open.
What prevents unchecked deployment?
A fixed script rebases and tests the changes before merging and restarting. It rolls back when the subsequent health check fails.
More details
Remaining steps
- A fixed deployment script rebased, tested, merged and restarted the app, with rollback after failed health checks.
About this account
A reviewing session converted short requests into work orders, reviewed engineer reports and controlled deployment. Engineer sessions implemented changes, with only one active engineering session at a time.
Firsthand account by u/CatalinMihaiSafta: https://www.reddit.com/r/ClaudeCode/comments/1x9v2gj/i_run_my_claude_code_agents_like_a_starship_crew/. Public RSS post and returned comments captured on 21 October 2026; RSS coverage is partial. Body eligibility passed at 0.96. Results are author-reported, not independently reproduced. Suggested prompt by Agents In Use, not the author's original prompt.
Credit: u/CatalinMihaiSafta on Reddit
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Git worktrees · herdr · Headless Chromium · CLAUDE.md
multi-agent · code-review · git-worktrees · deployment-checks
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.