haicue
agent work, held together
Install HaicueKnow what changed, what matters, and where to return.
- Follow live sessions, threads, and curated cue decks.
- See what settled, what awaits, and what needs your attention.
- Return to the right thread with the context intact.
Start with one real workflow: a code task, a meeting follow-up, or a messy brainstorm. See how to get started.
Bring your existing setup
Connect an installed agent using your existing subscription or local setup.
Haicue uses the provider authentication and local runtime you already configured.
Demo · Agent setup
Work on a project
“Fix the Cues panel on mobile.”
A project becomes a durable thread around the repository, the active agent session, and the decisions worth returning to. Inspect Git changes beside the conversation, and improve a rough prompt directly in the composer before sending it.
Come back to the project, not a pile of disconnected chats.
Demo · Project and prompt
Automate the routine
“Turn these review steps into a loop. Check new pull requests every hour on business days and tell me when one needs a decision.”
Describe the outcome in ordinary language. Haicue helps make the steps explicit, schedules the run, and leaves a visible result when your attention is actually needed.
Recurring work gets a cadence, an owner, and a clear return point.
Demo · Scheduled review
Let agents organize the work
“Use three agents in different Git worktrees. Keep them working for two hours, then bring me the decision.”
When one session is not enough, arrange a small working group around the job. Roles, isolated worktrees, and a time limit make the division of work legible before anything starts.
You set the shape of the work. The agents carry it out.
Demo · Roles and review
Make it your own
- “Build a LiveApp for this review.”
- “Capture cues from this meeting.”
- “Ask before updating Jira.”
Turn a proven way of working into a skill, bring purpose-built interfaces into the thread, and connect outside systems with explicit boundaries. The workspace grows around the work instead of forcing every job through one screen.
Reuse what works. Keep consequential actions visible and confirmed.
Demo · Cues and confirmation
