HagiCode Usage Tips

This FAQ reads the tips snapshot synchronized from Index during docs release builds and groups the advice into a browsable article.

Updated: 2026-06-0153 tipsData locale: en-USView source JSON on Index

Project Setup

8 items

1. Create a project before starting a session so HagiCode can manage files, context, and history together.

   project-first

2. Keep each project focused on related code and materials so sessions do not read unrelated context.

   project-boundary

3. Use a business or repository name for the project so it is easier to find later.

   project-name-clear

4. Record the current goal in the project so later sessions can pick up faster.

   project-goal-note

5. Put startup steps, account details, and common commands in the project notes to avoid repeating them.

   project-docs

6. Remove unrelated files before uploading materials so HagiCode can stay focused on the task.

   project-context-clean

7. Select the right project before opening a new session so the task lands in the correct context.

   project-before-session

8. When reviewing project history, start with the conclusion from the most recent completed session.

   project-history

Proposals and Scope

8 items

1. For larger changes, ask HagiCode to write a proposal before deciding whether to implement it.

   proposal-large-change

2. Make the proposal scope clear so the session does not keep expanding while it runs.

   proposal-scope

3. When you are unsure about the approach, ask HagiCode to list multiple options in the proposal.

   proposal-options

4. Risk notes in a proposal help you decide whether the change is worth continuing.

   proposal-risk

5. Breaking a proposal into tasks makes execution progress easier to follow.

   proposal-tasks

6. Review the proposal before implementation to catch missing details or a wrong direction early.

   proposal-review

7. Give each proposal a short, clear name so it is easier to find later.

   proposal-change-name

8. Record the result after a proposal is finished so you can revisit why the change was made.

   proposal-finish

Session Workflow

9 items

1. Give each session one clear goal so the result is easier to judge.

   session-single-goal

2. Start a session by stating the goal, constraints, and expected output directly.

   session-start-clear

3. When continuing an old task, tell HagiCode what has changed recently.

   session-context

4. In a long session, ask HagiCode for progress checkpoints along the way.

   session-checkpoint

5. Before pausing, record the next step so resuming the session takes less time.

   session-stop-point

6. After a session ends, read the result summary before deciding whether to keep asking follow-up questions.

   session-review-result

7. Correct the direction as soon as it feels wrong instead of overturning the whole session at the end.

   session-correction

8. If you know the relevant files, give HagiCode the file paths directly.

   session-files

9. When something fails, send HagiCode the full error message instead of only saying it failed.

   session-errors

Multi-Session Coordination

5 items

1. Before running sessions in parallel, split the goal into parts that do not conflict with each other.

   multi-session-plan

2. Use clear names for parallel sessions, such as proposal design, frontend implementation, or troubleshooting.

   multi-session-naming

3. When running sessions in parallel, try not to have them edit the same group of files.

   multi-session-isolation

4. After parallel sessions finish, review the results together before deciding which parts to use.

   multi-session-merge

5. For important tasks, let one session implement and another session focus on review.

   multi-session-review

Agent Roles

6 items

1. Give each agent a clear role, such as implementation, review, testing, or documentation cleanup.

   agent-role

2. When multiple agents collaborate, define their responsibility boundaries in advance.

   agent-boundary

3. During an agent handoff, preserve key conclusions, unfinished work, and important notes.

   agent-handoff

4. A review agent is better suited to finding issues than taking on a large rewrite at the same time.

   agent-review

5. A research agent can gather background first, then hand the work to an implementation agent.

   agent-research

6. Ask an agent for a short summary when you need to judge the next step quickly.

   agent-summary

Using Claude

3 items

1. Claude is well suited for analyzing long materials, comparing approaches, and organizing complex context.

   claude-analysis

2. Before complex design work, ask Claude to check whether the reasoning is complete.

   claude-design

3. When reading a large set of documents, Claude can help extract the key points and constraints.

   claude-docs

Using Codex

3 items

1. Codex is well suited for entering a repository, editing code, and running commands to verify the result.

   codex-implementation

2. When you do not know where to change something, ask Codex to search the project structure first.

   codex-navigation

3. After Codex makes changes, focus on which files changed and why those changes were made.

   codex-review-diff

code-server

4 items

1. When you need to inspect code manually, open the project with code-server.

   code-server-open

2. For small manual adjustments, code-server can be more convenient than switching local environments.

   code-server-edit

3. Before running a command in code-server, confirm that the terminal is in the target project.

   code-server-terminal

4. When adjusting an interface, use code-server to preview the actual result.

   code-server-preview

OmniRoute

4 items

1. OmniRoute can connect different models in one place so switching capabilities is easier.

   omniroute-provider

2. Use a faster model for simple tasks, then switch to a stronger model for complex ones.

   omniroute-model-choice

3. When a model is unavailable, OmniRoute fallback routes can reduce interruptions.

   omniroute-fallback

4. With OmniRoute, balance speed, quality, and cost based on how important the task is.

   omniroute-cost

HagiPower

3 items

1. Hagipower tracks your energy and activity across sessions so you can see how your usage adds up over time.

   hagipower-overview

2. Check your daily Hagipower achievements to stay on track with your coding goals and streaks.

   hagipower-daily-achievement

3. Balance Hagipower spending by mixing quick tasks with focused deep-work sessions to keep your energy steady.

   hagipower-energy-balance