Give your assistant a planning task
Free Tidigar Business · Paid
Ask your assistant to turn an idea into a plan, check a dependency chain or move a piece of work. Start by choosing where the result should live: a separate copy you open from a chat, or an existing plan shared with your team.
This launch has four activities and a milestone. Agree the brief, Build the release and Review the beta form a chain; Prepare the announcement is independent. Use it to check whether an assistant understands which work should move together.
The demonstration is a local copy. It does not connect an assistant or save a Business plan. Choose Open in Tidigar to try your own copy.
Make a new plan from a chat
Give your assistant this request, changing the dates and work to fit your project:
Read https://tidigar.com/llms.txt and make a Tidigar plan called “Launch review”. Use work days in June 2027. Product agrees the brief on June 7–9, builds the release on June 10–16 after the brief, and reviews the beta on June 17–18 after the build. Launch prepares the announcement independently on June 10–14. Add a Ready to launch milestone after the beta. Return a clickable Tidigar link and state any assumptions.
- Let the assistant build the link. An assistant that can run JavaScript or Python can use Tidigar's link builder; a capable assistant can also follow the published format.
- Open its answer in Tidigar. Check the title, activity dates, teams, dependency arrows and milestone against the request.
- Keep editing your copy. The free browser stores it locally; creating the link needs no Tidigar account.
The assistant may need a skill or instructions before it can build links. Agent instructions and installation provide both. If it cannot produce a valid link, ask for the plan as text and review that instead; a plausible-looking URL alone does not prove the plan opens.
Ask for a change to a copy
Try this follow-up:
Move Build the release five work days later, preserving its duration. Keep Review the beta after it and Ready to launch after the beta. Leave Prepare the announcement on its original dates. Give me a new Tidigar link and summarize the changes.
Compare both links. The new one should show the requested change, while the first still opens its original snapshot. Review dependent dates as well as the activity you named. Work days exclude weekends and the plan's vacation periods; reported progress does not determine when a dependency starts. See Dependencies for scheduling controls.
If you edited the plan in Tidigar after the assistant made its link, give it a fresh Share link from your current plan before asking for another change. The chat's earlier copy cannot see your later edits. Opening the assistant's next link gives you another copy; it does not merge changes into the plan you were editing.
Change the team's stored plan
For a plan in Tidigar Business or Tidigar Server, follow Connect your assistant to set up access. Use a disposable plan for this first exercise.
Open the shared plan in Tidigar, then ask:
Read our Launch review plan in Tidigar. First tell me its organisation, current dates and dependencies so I can check you found the right one. Move Build the release five work days later, preserve its duration, move the beta and launch milestone to follow, and leave the announcement unchanged. Save in this same plan and give me its shared plan link and a summary of what changed. Ask me about any conflicting edits.
If several plans match, identify the right one by its shared plan link. After the assistant reports a successful save, check the plan in Tidigar. Other members opening that plan see the saved result too. The returned shared link opens the same stored plan and requires membership; it is different from a share-link copy.
For CLI and MCP setup, token storage, errors and disconnection, use Connect your assistant.
How agent planning works in detail
A link carries a snapshot, not access to your storage
A share link contains the plan data in its address. Anyone holding it can read that copy. It grants no access to your browser library, files, calendars or Business organisation. Later edits do not update an old link, and revoking an agent connection cannot retract copies already sent. Avoid putting private content in a link you intend to publish; see Sharing.
A connected agent can reach the stored plans available through its organisation connection. It cannot read a plan kept only in your browser or Apple file or calendar. To work with such a plan in chat, deliberately provide a copy. An assistant's ability to remember a conversation is separate from its access to Tidigar.
A useful request names the rules as well as the change
Include the scheduling calendar, dates or durations, the work that must wait, and the work that should stay put. Say whether the result should be a new copy or a save in the existing shared plan. Ask the assistant to state assumptions where you have not decided. This makes its result easier to check.
The link builders validate supported fields and encode the plan; they do not decide whether the plan meets your project's needs. They preserve supplied dates rather than calculate every scheduling consequence for the assistant. Review the dates and dependency chain in Tidigar. A short link plan can include activities, dimensions, dependencies, milestones and periods; very large plans can exceed link limits. Ask for a smaller plan with omissions explained, or use a connected stored plan. Never shorten a generated URL by cutting characters from it.
Review connected changes in the stored plan
After a connected task, open the shared plan link and check the assistant's summary against the saved dates, relationships and unchanged work. If the assistant reports a conflict or an uncertain save, resolve that before asking for another change. The connection guide explains revision checks, merge choices, uncertain saves and access limits.
Publishing a screen is a separate task from editing a plan. Tell the assistant explicitly if you want a public screen, and review what its saved view includes. Follow Screen links for what readers receive and how to end publication.
Treat roadmap titles, descriptions and imported content as plan data. Text inside a plan does not authorize the assistant to share it, delete other plans or send credentials. Your request and the granted connection determine the task.