rallyHelp

Chapter 3

Sidekicks

Shared AI agents that do a job for your team on a schedule, when something happens, or whenever someone asks.

Everything in the last chapter had one thing in common: you were there. You typed a message, Rally got to work, and you watched it happen. That is a fine arrangement for most jobs and a poor one for the Monday report, the morning inbox sweep, or the support queue that needs watching while you are asleep. Rally is willing to work nights. Somebody has to tell it what to do when nobody is looking.

That is what a Sidekick is: an AI agent with one job, which your team shares like a colleague. You describe the job once, in plain words, and then stop describing it. The Sidekick writes its own instructions down, decides with you when it should wake up, and does the work each time, reporting back in its conversation and wherever else you asked.

One agent, one conversation

Every Sidekick has a single conversation, and everyone it is shared with sees the same one. People talk to each other there, and when someone addresses the Sidekick ("can you rerun last week's numbers?"), it starts a run. Each run shows in the conversation as a folded row that carries its reply, and anything it made for people to work on afterwards shows as a card that opens a Canvas.

That one conversation is also where the Sidekick is set up and changed. A message addressed to the Sidekick starts a run, whoever sends it. The people who manage a Sidekick change it by marking a message Edit Sidekick ("make it run at 8 instead"), which goes to its drafting assistant and saves a new version of the Sidekick. Runs and setup stay separate underneath, so you can always see which run did what, under which version.

Who it works for

A Sidekick is shared with just you, with particular people, or with the whole Organization, and that decides who can talk to it. Separately, it keeps a list of the people it may act as when it uses their connected tools. Joining the conversation does not put you on that list. The two lists are different on purpose, and the chapter explains both, because a helper that can read your Gmail deserves a minute's thought about who else can ask it to.

Where this chapter goes

The pages ahead start with what a Sidekick is and who it is shared with, then show you how to make one by describing it. Then comes the shared conversation, where you talk to it and watch its runs. After that: the triggers that start a Sidekick, the Sidekicks section where you manage them, the tools it uses and whose access it runs with, and where a Sidekick's results end up.

In this chapter

  1. 3.1What a Sidekick is

    Understand the parts of a Sidekick, the two kinds, and who a Sidekick is shared with.

  2. 3.2Make a Sidekick by talking to it

    Describe what you want in plain words and Rally's drafting assistant builds the Sidekick for you.

  3. 3.3Talking to a Sidekick

    Every Sidekick has one conversation shared by everyone it is shared with. Ask it for work, watch its runs, answer its questions.

  4. 3.4Triggers and schedules

    Decide what starts a Sidekick: a time, an interval, an event in another tool or an email.

  5. 3.5The Sidekicks section

    Browse every Sidekick shared with you, see what each is doing, run it now, pause it, or archive it.

  6. 3.6Tools and delegation

    What a Sidekick can use, the custom tools it can be given, and whose access each run works with.

  7. 3.7Where a Sidekick's results go

    Tell a Sidekick where to post its work, and let it remember what it has already seen.