How to use Claude Code with your team

Claude Code is useful in one terminal. It becomes more useful when the team can see what it tried, what it ran, and what came back.

Ano gives teams three surfaces for that.

1. Press ⌘J inside a channel

Use ⌘J for ad-hoc work that starts in a channel. Claude Code opens with the channel context loaded, can call the workspace’s CLIs and MCP servers, and posts the result back into the same channel.

Use it when:

• The question is yours, but the answer helps the channel.
• The work is one-off.
• You want to drive the session yourself.

Skip it when the same request repeats across the team. That is usually a coworker.

Read Press ⌘J: a shell in every channel for the deeper version.

2. Add an AI coworker

A coworker is a named, workspace-shared Claude Code agent with a purpose and a toolset. Anyone can mention it. It reads the thread, calls tools, and replies where the work started.

Use it when:

• Multiple people ask the same kind of question.
• The job fits in one paragraph.
• Three or fewer tools can do most of the work.

Skip it when the job is vague. “Help with sales stuff” is not a coworker. “List at-risk HubSpot deals every Friday” is.

Read What is an AI coworker? and Designing a useful AI coworker.

3. Drive Ano from a terminal

Use the Ano CLI when the work is scheduled, triggered, or already part of a shell pipeline.

ano messages read --channel launch --json \
  | claude "summarize this week's launch thread" \
  | xargs -I {} ano messages send "{}" --channel launch

Use it when:

• A cron job, CI step, or webhook triggers the work.
• The workflow is headless.
• The output belongs in a channel.

Skip it when a person needs to approve the next step. Use ⌘J or a coworker so the decision stays visible.

Decision table

These surfaces are complementary. A healthy workspace uses all three.

Example day

• 09:30: An engineer presses ⌘J in #engineering to inspect a CI regression.
• 10:00: The team turns the recurring incident-summary task into an oncall-helper coworker with gh, git, and PagerDuty access.
• 14:00: GitHub Actions posts a failed build to #ci through ano messages send.

Same model, three ownership patterns.

Avoid

• A generic “Claude Slackbot.” It answers from the outside instead of working in the channel.
• Manual copy-paste from Claude into chat. Use ⌘J.
• One do-everything coworker. Small agents are easier to trust and fix.

Going deeper

Start with Channels, threads, and DMs: the Ano model if your team is new to the workspace model.