Set your typical top-up amount to show the usage chart
Run codex in the terminal to authenticate; Squid reads ~/.codex/auth.json.
Auto-detect from browserReads this machine's Chrome cookies directly — only works over a direct connection to 127.0.0.1/localhost, not through Tailscale or another proxy.
DevTools → Application → Cookies → claude.ai → sessionKey
Run cursor-agent in the terminal to authenticate Cursor.
Help
On mobile: at the bottom of the chat, swipe up to refresh
Input syntax
#topic@agent messagesession — FIFO queued per agent
#topic@agent!N messageadhoc — parallel, last N selected as context
#topic@agent! messageadhoc — parallel, no context
#topic@agent ! commandqueued native shell — exact output, no LLM; arbitrary local code
#topictype # to browse & search topics
#topic@type @ to browse agents, tab to last used
Input box icons
toggle to show only bookmarked responses — tap when empty to browse bookmarks
toggle to show only your prompts in history
filter history to current route (#topic@agent)
search within current route
cleaning_servicesinsert /clear — clears session for next message
archivestash prompt for later — tap when empty to open recent stashed prompts
pinned context — responses pinned here inject as context in adhoc turns
AgentSquid Commands — type / to browse
/clearclear session — next message starts fresh (all backends)
/stopkill running process for current topic
/stopallkill + drain queue for current topic
/deqdrain entire pending queue
/deq Nremove Nth item (1=first, -1=last)
/f, /filterfilter history using the same scope syntax as search
Canonical key (saved to DB, identifies this workflow)
Branch breakdown
Fully expanded form
Syntax
#topic1which topic (conversation) this step runs in
@agent1which agent handles this step
!fresh — start a new session instead of continuing the agent's existing one
>one-way handoff to the next step
=>alias for > — same meaning, alternate spelling
,independent branches — each side runs on its own, not chained together
#t3,#t1@a1a bare atom borrows its missing half from the nearest fully-explicit atom before it — or, if none precedes it yet, from the first fully-explicit atom anywhere in the list (here, #t3 becomes #t3@a1 even though it's written first)
+join — merges multiple steps into one downstream consumer; valid as the origin (feeding the one hop) or, under <>/<N>, as the target (its return leg is the consumer)
<> / <N>request/response round trip; <N> repeats it N times
<N:1d>round trip, waiting the given duration between every hop (out and back), both directions equally
=N>repeat this one-way handoff N times back to back, no delay
=N:1d>repeat N times, spaced by the given duration
=:1d>count omitted (defaults to 1), waiting the given duration before sending