Skip to main content
Your agent chooses and calls these tools. You do not call them yourself. Use this page to understand what your agent does, and to ask for a tool by name. Sends means that the tool delivers something to another person. Alike tells your agent to ask you before it calls a tool that sends. Alike does not block these tools. Only invitations wait on Alike’s side until you confirm.

Start and orient

Log your own work

These tools change only your own items. The agent calls them without asking you.

Your other sessions

These tools work only between your own sessions. They need no confirmation.

Colleagues

Your settings

Key inputs

You do not write tool inputs yourself. But if you know the values, you can ask for them by name. For example: “Search only my past agent sessions.”

Work item anchors

resolve_work_item accepts one of three anchor types: Alike ignores the difference between upper case and lower case in anchors. A pull request or issue anchor links to the task that Alike already made from that pull request or issue, if you connected the tool. Alike refuses an anchor value that is too long. It does not shorten it. When the agent links the same session to the same work item again, it gets a short update with what changed, not the full brief. To get the full brief again, for example after the agent’s context was compacted, ask: “Get the full Alike brief for this work again.”

Code anchors on a decision

record_decision accepts these code anchors: repository, branch, pr_number, issue_id, and paths. Give all the anchors that you know. See Decisions.

Search types

search_environment searches all your source types by default. To limit the search, the agent names one or more types, for example agent_session for your past sessions. read_agent_session opens the transcript of a session result around the matched turn. To read a session’s summary item, the agent finds it by title with query_entities and reads the item’s ID with get_entity. See Search types.

Details of one item

get_entity can add these details to an item: To see where a fact came from, ask: “Where did Alike get this decision from?”

Reasons to dismiss an item

dismiss_entity accepts a reason: not_relevant, duplicate, incorrect, not_a_task, spam, or other. The reasons incorrect, not_a_task, spam, and not_relevant also tell Alike that it found the item by mistake.

Messages and replies

More tools

Builders do not see these tools at first. To get them, ask your agent: “Call Alike’s get_more_tools.” The agent then lists the tools again. If your client does not refresh its tool list by itself, reconnect the server or restart the client. If the tools disappear later, ask the agent to call get_more_tools again.
If your calendar is connected, calendar tools change your real calendar. add_event_to_plan and confirm_event_in_plan can send invitations to attendees. cancel_event can notify attendees.

Change a colleague’s item

Your agent cannot change a colleague’s item directly. It must choose one of two modes:
  • suggest_to_owner: sends the change to the owner as a proposal. The owner accepts, counters, or declines. This sends a message to the owner.
  • create_local: makes a private copy of the item for you. Nobody else sees the change.
The planning and calendar tools ask for confirmation first when you use them on a colleague’s item. With confirmation, they change your private copy.